Date   
Pull Request Updated #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request updated by Christianlm:

#579 Updated dictionaries and phonemes statements tested on january 2019

IT: Improved statements for phoneme ss

It: Improved rules pronounciation and exceptions

[espeak-ng:master] new issue: festival and espeak phonemes compatibility #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by dmikushin:
#580 festival and espeak phonemes compatibility

Hello world in Festival is [u'hh', u'ax', u'l', u'ow', u'w', u'er', u'l', u'd']

Hello world in eSpeak is [u'h', u'\u0259', u'l', u'o\u028a', u'\nw', u'\u025c\u02d0', u'l', u'd']

Is there already a translation table between their different sets of phonemes, or is there a relatively simple algorithm to create such a translation?

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

4 New Commits:

[espeak-ng:master] By chrislm <llajta2012@...>:
133fe55d0845: IT: Improved statements for phoneme ss

It: Improved rules pronounciation and exceptions

Modified: dictsource/it_list
Modified: dictsource/it_listx
Modified: dictsource/it_rules
Modified: phsource/ph_italian


[espeak-ng:master] By chrislm <llajta2012@...>:
388c1bfa01f4: ES: Fixes pronounciation of the word emoji in spanish language.

Modified: dictsource/es_list


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
7c58e2d8fb46: it: fix phoneme checksum

Modified: tests/language-phonemes.test


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
a95f09f674be: hyw: fix dictionary filename

Modified: dictsource/hy_rules


[espeak-ng:master] New Comment on Pull Request #579 Updated dictionaries and phonemes statements tested on january 2019
By valdisvi:

Thanks for contribution! I included your changes in master and also updated test with different phoneme checksum.


[espeak-ng/espeak-ng] Pull request closed by valdisvi:

#579 Updated dictionaries and phonemes statements tested on january 2019

IT: Improved statements for phoneme ss

It: Improved rules pronounciation and exceptions

[espeak-ng:master] reported: festival and espeak phonemes compatibility #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #580 festival and espeak phonemes compatibility
By valdisvi:

In general, there should be one-to-one mapping between phonemes. I have no idea in which language this "Hello world" is written, but output from espeak-ng seems like IPA output (produced with e.g. espeak-ng -ven --ipa "hello world"), where Unicode letters e.g. ə are garbled to escape sequence e.g. \u0259. Mapping between Latinized phonetic writing (e.g. just `espeak-ng -ven "hello world") should be easier. Phonemes are documented in Phoneme Tables page and configuration files are located in phsource folder.

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by Giovani93:
#581 Adding Tagalog /Filipino language to Espeak

Hello. Here is Marco from Slovakia. I have one idea to You. Ofcourse, I am not speaker of this language, but please, can You add Tagalog/Filipino language to Espeak? I use Espeak NG with NVDA to learn new languages, because I am blind and It'll be maybe good idea to do It. Thank You. best regards Marco Oros


[espeak-ng:master] New Issue Created by Giovani93:
#582 Adding Hebrew language to Espeak

Hello. In Espeak, there is support for reading Hebrew letters, but there is not any support for Hebrew language. Maybe there are some people, who speaks Hebrew and they are programmers. I am not Hebrew native speaker, but I use Espeak to learn new languages. I have Espeak NG in NVDA and ofcourse, I use Espeak not only in My native language Slovak, but also in another languages to good understanding this language, for example English, or Spanish ETC. So please, could You add Hebrew language to Espeak? Thank You. best regards Marco Oros

[espeak-ng:master] new issue: Sequence of punctuation signs handling #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by BenTalagan:
#583 Sequence of punctuation signs handling

Hi,

Generally, espeak is not fond of multiple punctuation signs like !!! or ?!! . It will tend to parse them as multiple clauses (which is logical) and as such, because the last signs of the sequence are isolated in their own clause, they will be spelled by espeak. E.g. 'Hi !!!' will result in 'Hai exclamation'. This should probably be taken into account since it's quite frequent in modern written speech. It also seems related to #369 to me, isn't it?

Best.

[espeak-ng:master] new issue: emscripten demo broken, probably highlights underlying problem linked to dictionary compilation #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave like this on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work with the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environnement (emscripten) and not the other (unix/mac) may highlight something more nasty behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affects the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something more nasty behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affects the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben


[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something nastier behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affects the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben


[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something nastier behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affect the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben


[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something nastier behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affect the compilation. These flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben

Re: Updates to Github #github

Karl Eick
 

Why this was shown four times? Was the issue revised?

Am 14.02.2019 um 18:31 schrieb espeak-ng@groups.io Integration:

[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something more nasty behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affects the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben


[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something nastier behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affects the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben


[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something nastier behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affect the compilation. This flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben


[espeak-ng:master] New Issue Created by BenTalagan:
#584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation

Hi all,

The emscripten demo has been broken this year : currently the symptom is that it will block for quite a while and then crash with a :

Bad rules data in 'en_dict' at 0xff948a30

It took me a while to bisect it but the demo started to behave badly on this precise commit : 55c64036e0335b75910e7354d92c98ff3845d032 although it would work on the precedent commit 0e91fcbc043cf363cccf3d6810afdfa0ab77472f.

Seems to me that having a crash in one environment (emscripten) and not the other (unix/mac) may highlight something nastier behind the hood.

One remark, the demo is also out of date, emscripten has evolved and some modifications affect the compilation. These flags should be added to the Makefile for EM_CXXFLAGS : -s FORCE_FILESYSTEM=1 -s WASM=0 and in the post.js, Runtime. should be removed before addFunction and removeFunction. I can prepare a PR if it helps, but it won't fix the underlying dictionary compilation pb.

Ben

Re: Updates to Github #github

Valdis Vitolins
 

Why this was shown four times? Was the issue revised?
Yes.

Valdis

[espeak-ng:master] reported: emscripten demo broken, probably highlights underlying problem linked to dictionary compilation #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By valdisvi:

With this commit (and some other changes later) espeak-ng has changed file format for compiled rules (..dict files located in espeak-ng-data folder). This error may occur when newer engine is used with older data files or vice versa.

[espeak-ng:master] reported: Adding Tagalog /Filipino language to Espeak #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #581 Adding Tagalog /Filipino language to Espeak
By valdisvi:

Espeak may not be the best tool to learn spoken language, because of different (and not always great) quality of pronunciation for it. If we would add basic support for Tagalog/Filipino, pronunciation quality would be very low and would not be usable for learning. I suggest https://www.101languages.net/ web site, e.g. this for Tagalog as a start.

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By BenTalagan:

When I compile for emscripten, I compile from scratch each time so as to avoid taking the risk of embedding old data. This is my complete build flow (from root directory) :

make clean make distclean ./configure --prefix=/usr --without-async --without-mbrola --without-sonic make en cd src/ucd-tools make clean emconfigure ./configure emmake make clean emmake make cd ../.. emconfigure ./configure --prefix=/usr --without-async --without-mbrola --without-sonic emmake make clean emmake make src/libespeak-ng.la cd emscripten emmake make clean emmake make So I may be wrong, but imho I don't think I'm using outdated data, just those who are present at the commit in question, and looking at the date of the generated data files, these data seem to be definitely repacked at each build. So if it's not a problem of version compatibility like I think, my first guess would be some problem of packing and alignment which is common between compilers if you don't take extra care when generating binary data.


[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By BenTalagan:

When I compile for emscripten, I compile from scratch each time so as to avoid taking the risk of embedding old data. This is my complete build flow (from root directory) :

make clean
make distclean
./configure --prefix=/usr --without-async --without-mbrola --without-sonic
make en
cd src/ucd-tools
make clean
emconfigure ./configure
emmake make clean
emmake make
cd ../..
emconfigure ./configure --prefix=/usr --without-async --without-mbrola --without-sonic
emmake make clean
emmake make src/libespeak-ng.la
cd emscripten
emmake make clean
emmake make

So I may be wrong, but imho I don't think I'm using outdated data, just those who are present at the commit in question, and looking at the date of the generated data files, these data seem to be definitely repacked at each build. So if it's not a problem of version compatibility like I think, my first guess would be some problem of packing and alignment which is common between compilers if you don't take extra care when generating binary data.

[espeak-ng:master] new issue: long text with repeating pattern produces rogue phoneme output #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by ultrasound1372:
#585 long text with repeating pattern produces rogue phoneme output

I have come across a rather strange bug brought to me by a user on twitter. I use assistive technology, namely NVDA, and use it daily to read things such as twitter. I normally use a different synthesizer, however in this tweet a friend of mine quoted saying it makes eSpeak make hilarious noises. Naturally I had to switch. The output is completely different than what you would expect from such a string. The text will be pasted below, with a recording of a different synthesizer that I use reading the same text and producing output that is more typical for the English language rules. It is worth noting that previous versions of eSpeak, before the NG rebranding, are not subject to this bug. Bananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananananananaananan

ETI rogue banana string.zip

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request opened by BenTalagan:

#586 Fix for newer versions of emscripten

This is a fix in order to compile the emscripten demo with recent versions of emscripten.

The default behaviour of emscripten is now to compile with WASM option, generating a different data file and forcing async loading. For now, I propose to just stay the closest as possible to what was done before and keep a sync loading by just using WASM=0.

File System function import in the module has also become an option in emscripten, and we need it so the flag should be passed explicitly : FORCE_FILESYSTEM=1

The Runtime functions are now imported directly without scoping the Runtime module: updated accordingly.

That's all for the changes.


[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By BenTalagan:

By the way, here is a PR #586 to be able to compile again with newer versions of emscripten.


[espeak-ng/espeak-ng] Pull request updated by BenTalagan:

#586 Fix for newer versions of emscripten

This is a fix in order to compile the emscripten demo with recent versions of emscripten.

The default behaviour of emscripten is now to compile with WASM option, generating a different data file and forcing async loading. For now, I propose to just stay the closest as possible to what was done before and keep a sync loading by just using WASM=0.

File System function import in the module has also become an option in emscripten, and we absolutely need it, so the flag should be passed explicitly : FORCE_FILESYSTEM=1

The Runtime functions are now imported directly without scoping the Runtime module: updated accordingly.

That's all for the changes.

[espeak-ng:master] reported: long text with repeating pattern produces rogue phoneme output #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #585 long text with repeating pattern produces rogue phoneme output
By valdisvi:

Provided record in definitely not from the English language. You can test, listen and download proper sample from online test page.

[espeak-ng:master] reported: long text with repeating pattern produces rogue phoneme output #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #585 long text with repeating pattern produces rogue phoneme output
By ultrasound1372:

Ah, yes the testing page isn't subject to that it seems, as long as no line wrapping is being honored. I'll open this with NVDA then, maybe the commit they're on is a little outdated and subject to this bug. According to their change log they are on commit 919f3240cbb of espeak NG.

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By valdisvi:

I tried to test your pull request, but I got problem executing emmake make in emscripten folder (step 4. in espeakng.js):

python /usr/share/emscripten/tools/webidl_binder.py espeakng_glue.idl glue
Traceback (most recent call last):
  File "/usr/share/emscripten/tools/webidl_binder.py", line 15, in <module>
    import WebIDL
ImportError: No module named WebIDL
Makefile:122: recipe for target 'glue.cpp' failed
make: *** [glue.cpp] Error 1

How did you solve this? (I'm using 64-bit (L)Ubuntu 16.04)


[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By valdisvi:

I tried to test your pull request #586, but I got problem executing emmake make in emscripten folder (step 4. in emscripten documentation):

python /usr/share/emscripten/tools/webidl_binder.py espeakng_glue.idl glue
Traceback (most recent call last):
  File "/usr/share/emscripten/tools/webidl_binder.py", line 15, in <module>
    import WebIDL
ImportError: No module named WebIDL
Makefile:122: recipe for target 'glue.cpp' failed
make: *** [glue.cpp] Error 1

How did you solve this? (I'm using 64-bit (L)Ubuntu 16.04)


[espeak-ng:master] Issue #585 long text with repeating pattern produces rogue phoneme output closed by ultrasound1372.

[espeak-ng:master] reported: emscripten demo broken, probably highlights underlying problem linked to dictionary compilation #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By BenTalagan:

On my side I'm on macos Mojave with the default python install, and I use emscripten via a git pull of emsdk (the tool for managing multiple versions of emscripten). From emsdk, I have installed and activated the 1.38.26 of emscripten.

Reading from the net, your problem looks more like a problem of python installation itself (used by the emscripten toolchain) - it's the first time I see this error.

You can check on the installation page of emscripten that you've not missed a point during the install, here : https://emscripten.org/docs/getting_started/downloads.html

or maybe try to update your python installation ? What is your version? 2.7.12 is at least required (stated by the emscripten page).

[espeak-ng:master] reported: emscripten demo broken, probably highlights underlying problem linked to dictionary compilation #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #584 emscripten demo broken, probably highlights underlying problem linked to dictionary compilation
By BenTalagan:

On my side, I'm on MacOs Mojave with the default python install, and I use emscripten via a git pull of emsdk (the tool for managing multiple versions of emscripten). From emsdk, I have installed and activated the 1.38.26 version of emscripten.

Reading from the net, your problem looks more like a problem of python installation itself (used by the emscripten toolchain) - it's the first time I see this error.

You can check on the installation page of emscripten that you've not missed a point during the install, here : https://emscripten.org/docs/getting_started/downloads.html

or maybe try to update your python installation ? What is your version? 2.7.12 is at least required (stated by the emscripten page).