Date   
Re: espeak-ng and some letters

Reece H. Dunn
 

On Thu, May 4, 2017 at 10:32 am, Simon Eigeldinger wrote:

Hi all,

I just figured out while updating nvda that they also seemed to have
updated the synth.

espeak ng now seems to have some weird issues in german with some letters.
like the n and the s in special constelations.
as well as the c, k and ck.

Thanks for the report. I have identified the cause of this regression and am working on a fix. There is also a report of the problem at https://github.com/espeak-ng/espeak-ng/issues/250.

I also have an idea on reducing the possibility of unwanted regressions in the future.

Kind regards,

Reece

Updates to Github #github

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

[espeak-ng:master] Label added to issue #250 some words in NVDA are starting to speak incorrectly since the last espeak NG update for it by derekriemer.


[espeak-ng:master] Label added to issue #250 some words in NVDA are starting to speak incorrectly since the last espeak NG update for it by derekriemer.


[espeak-ng:master] New Issue Created by derekriemer:
#250 some words in NVDA are starting to speak incorrectly since the last espeak NG update for it

Hi:

NVDA is currently incubating https://github.com/nvaccess/nvda/pull/7115 which is causing some words to break in english US. Here are a list I have compiled. compiled compressional condolence current continue

The issue is that the c at the beginning of the words is way to short, so it kind of sounds like the second vowel is simply being shortened. I am not sure how to explain this without telling someone the pronunciation I expect. as this will affect NVDA, cc @jcsteh @MichaelDCurran

Re: espeak-ng and some letters

David Hilton
 

I just check with the last table release in Spanish, there does not seem to be any major change, no changes to the exiting on some of the dip have happened between old and new generations. The only alveolar uvular or guttural I can think of is final hour, which has always made that sound. Also which accents are you using, Latin America or Spain? There are slight differences in the pronunciation of consonants between those two accents of Espeak.

Sent from my iPhone

On May 4, 2017, at 4:17 PM, Sukil Etxenike via Groups.Io <sukiletxe=yahoo.es@groups.io> wrote:

Hi,

What happened to Spanish? Espeak NG now literally deletes the word initial y's (try yo, ya, yate), and the /r/ sound doesn't sound right (it sounds as if it wasn't an alveolar trill anymore, but a postalveolar, or even more back, one). Also, the first sound in the dypthong in /oi/ sounds slightly more open than what it was before. And finally, the commbination /dy/ gives the approximant sound for the dd, rather than the plosive one.

Thanks,

Sukil

El 04/05/2017 a las 21:34, Simon Eigeldinger escribió:
Hi Valdis,

Yes thats the obvious one.
though when you are sitting there with a headset the whole day listening to the computer you kind of notice the small ones as well. *smile*

greetings,
simon


Am 04.05.2017 um 21:27 schrieb Valdis Vitolins:
The most noticeable difference I can hear is missing n at the end of
"stern".
For now I could say that it should be related to phoneme definitions or
sound generation, as phoneme representation is still the same.

Valdis
Hi Valdis,

Yes it does sound not right.

Here's another example:
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=dr
ucker,+lampe,+computer,+stern,+sterne&formmethod=get


Am 04.05.2017 um 20:30 schrieb Valdis Vitolins:

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.
Does it sounds wrong on http://odo.lv/Espeak?language=en to you?
E.g.
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=
Druc
ker%2C+lampe%2C+guten+morgen.&formmethod=get&language=en
Valdis

Hi all,

I just figured out while updating nvda that they also seemed to
have
updated the synth.

espeak ng now seems to have some weird issues in german with some
letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something
happened
to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in
computer
starts to flow apart. the same with lampe where the p kind of is
weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
geprüft.
https://www.avast.com/antivirus







Re: espeak-ng and some letters

David Hilton
 

Are any of these changes reflected in the last stable release of nonvisual desktop access? I have been trying to work on the Spanish you speak, and have asked assistance from several people. On get hub, I noticed someone had made a modified for Version of Espeak, fixing some accent Tatian with Spanish. But I do not know if these changes were applied to Espeak and G new generation.

Sent from my iPhone

On May 4, 2017, at 4:17 PM, Sukil Etxenike via Groups.Io <sukiletxe=yahoo.es@groups.io> wrote:

Hi,

What happened to Spanish? Espeak NG now literally deletes the word initial y's (try yo, ya, yate), and the /r/ sound doesn't sound right (it sounds as if it wasn't an alveolar trill anymore, but a postalveolar, or even more back, one). Also, the first sound in the dypthong in /oi/ sounds slightly more open than what it was before. And finally, the commbination /dy/ gives the approximant sound for the dd, rather than the plosive one.

Thanks,

Sukil

El 04/05/2017 a las 21:34, Simon Eigeldinger escribió:
Hi Valdis,

Yes thats the obvious one.
though when you are sitting there with a headset the whole day listening to the computer you kind of notice the small ones as well. *smile*

greetings,
simon


Am 04.05.2017 um 21:27 schrieb Valdis Vitolins:
The most noticeable difference I can hear is missing n at the end of
"stern".
For now I could say that it should be related to phoneme definitions or
sound generation, as phoneme representation is still the same.

Valdis
Hi Valdis,

Yes it does sound not right.

Here's another example:
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=dr
ucker,+lampe,+computer,+stern,+sterne&formmethod=get


Am 04.05.2017 um 20:30 schrieb Valdis Vitolins:

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.
Does it sounds wrong on http://odo.lv/Espeak?language=en to you?
E.g.
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=
Druc
ker%2C+lampe%2C+guten+morgen.&formmethod=get&language=en
Valdis

Hi all,

I just figured out while updating nvda that they also seemed to
have
updated the synth.

espeak ng now seems to have some weird issues in german with some
letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something
happened
to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in
computer
starts to flow apart. the same with lampe where the p kind of is
weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
geprüft.
https://www.avast.com/antivirus







Re: espeak-ng and some letters

Sukil Etxenike <sukiletxe@...>
 

Hi,

What happened to Spanish? Espeak NG now literally deletes the word initial y's (try yo, ya, yate), and the /r/ sound doesn't sound right (it sounds as if it wasn't an alveolar trill anymore, but a postalveolar, or even more back, one). Also, the first sound in the dypthong in /oi/ sounds slightly more open than what it was before. And finally, the commbination /dy/ gives the approximant sound for the dd, rather than the plosive one.

Thanks,

Sukil

El 04/05/2017 a las 21:34, Simon Eigeldinger escribió:
Hi Valdis,

Yes thats the obvious one.
though when you are sitting there with a headset the whole day listening to the computer you kind of notice the small ones as well. *smile*

greetings,
simon


Am 04.05.2017 um 21:27 schrieb Valdis Vitolins:
The most noticeable difference I can hear is missing n at the end of
"stern".
For now I could say that it should be related to phoneme definitions or
sound generation, as phoneme representation is still the same.

Valdis
Hi Valdis,

Yes it does sound not right.

Here's another example:
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=dr
ucker,+lampe,+computer,+stern,+sterne&formmethod=get


Am 04.05.2017 um 20:30 schrieb Valdis Vitolins:

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.
Does it sounds wrong on http://odo.lv/Espeak?language=en to you?
E.g.
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=
Druc
ker%2C+lampe%2C+guten+morgen.&formmethod=get&language=en
Valdis

Hi all,

I just figured out while updating nvda that they also seemed to
have
updated the synth.

espeak ng now seems to have some weird issues in german with some
letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something
happened
to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in
computer
starts to flow apart. the same with lampe where the p kind of is
weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
geprüft.
https://www.avast.com/antivirus





Re: espeak-ng and some letters

Simon Eigeldinger
 

Hi Valdis,

Yes thats the obvious one.
though when you are sitting there with a headset the whole day listening to the computer you kind of notice the small ones as well. *smile*

greetings,
simon


Am 04.05.2017 um 21:27 schrieb Valdis Vitolins:

The most noticeable difference I can hear is missing n at the end of
"stern".
For now I could say that it should be related to phoneme definitions or
sound generation, as phoneme representation is still the same.
Valdis
Hi Valdis,

Yes it does sound not right.

Here's another example:
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=dr
ucker,+lampe,+computer,+stern,+sterne&formmethod=get


Am 04.05.2017 um 20:30 schrieb Valdis Vitolins:

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.
Does it sounds wrong on http://odo.lv/Espeak?language=en to you?
E.g.
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=
Druc
ker%2C+lampe%2C+guten+morgen.&formmethod=get&language=en
Valdis

Hi all,

I just figured out while updating nvda that they also seemed to
have
updated the synth.

espeak ng now seems to have some weird issues in german with some
letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something
happened
to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in
computer
starts to flow apart. the same with lampe where the p kind of is
weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
geprüft.
https://www.avast.com/antivirus



--
Simon Eigeldinger
Follow me on Twitter: http://www.twitter.com/domasofan/
E-Mail: simon.eigeldinger@...
MSN: simon_eigeldinger@...
ICQ: 121823966
Jabber: domasofan@...

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: espeak-ng and some letters

Valdis Vitolins
 

The most noticeable difference I can hear is missing n at the end of 
"stern".
For now I could say that it should be related to phoneme definitions or
sound generation, as phoneme representation is still the same.

Valdis

Hi Valdis,

Yes it does sound not right.

Here's another example:
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=dr
ucker,+lampe,+computer,+stern,+sterne&formmethod=get


Am 04.05.2017 um 20:30 schrieb Valdis Vitolins:

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.
Does it sounds wrong on http://odo.lv/Espeak?language=en to you?
E.g.
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=
Druc
ker%2C+lampe%2C+guten+morgen.&formmethod=get&language=en
Valdis

Hi all,

I just figured out while updating nvda that they also seemed to
have
updated the synth.

espeak ng now seems to have some weird issues in german with some
letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something
happened
to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in
computer
starts to flow apart. the same with lampe where the p kind of is
weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
geprüft.
https://www.avast.com/antivirus



Re: espeak-ng and some letters

Simon Eigeldinger
 

Hi Valdis,

Yes it does sound not right.

Here's another example:
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=drucker,+lampe,+computer,+stern,+sterne&formmethod=get


Am 04.05.2017 um 20:30 schrieb Valdis Vitolins:

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.
Does it sounds wrong on http://odo.lv/Espeak?language=en to you?
E.g.
http://odo.lv/Espeak?eslang=-vde&speed=160&output=-w&debug=-x&text=Druc
ker%2C+lampe%2C+guten+morgen.&formmethod=get&language=en
Valdis
Hi all,

I just figured out while updating nvda that they also seemed to have
updated the synth.

espeak ng now seems to have some weird issues in german with some
letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something happened
to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in
computer
starts to flow apart. the same with lampe where the p kind of is
weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus



--
Simon Eigeldinger
Follow me on Twitter: http://www.twitter.com/domasofan/
E-Mail: simon.eigeldinger@...
MSN: simon_eigeldinger@...
ICQ: 121823966
Jabber: domasofan@...

Re: espeak-ng and some letters

Valdis Vitolins
 

When I compared current eSpeakNG build with few months older build,
I couldn't hear noticeable differences.

Does it sounds wrong on http://odo.lv/Espeak?language=en to you?

E.g.

Valdis

Hi all,

I just figured out while updating nvda that they also seemed to have
updated the synth.

espeak ng now seems to have some weird issues in german with some letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something happened to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in computer
starts to flow apart. the same with lampe where the p kind of is weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.



espeak-ng and some letters

Simon Eigeldinger
 

Hi all,

I just figured out while updating nvda that they also seemed to have
updated the synth.

espeak ng now seems to have some weird issues in german with some letters.
like the n and the s in special constelations.
as well as the c, k and ck.

The word computer now sounds weird and strange as something happened to
the c as it kind of got way too soft.
as well as the german word drucker, lampe where the ck like in computer
starts to flow apart. the same with lampe where the p kind of is weird.
in the word stern as well. the n is barely hearable.


anyone figured that out as well?

Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Updates to Github #github

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

[espeak-ng:master] New Issue Created by derekriemer:
#250 some words in NVDA are starting to speak incorrectly since the last espeak NG update for it

Hi:

NVDA is currently incubating https://github.com/nvaccess/nvda/pull/7115 which is causing some words to break in english US. Here are a list I have compiled. compiled compressional condolence current continue

The issue is that the c at the beginning of the words is way to short, so it kind of sounds like the second vowel is simply being shortened. I am not sure how to explain this without telling someone the pronunciation I expect. as this will affect NVDA, cc @jcsteh @MichaelDCurran


[espeak-ng:master] New Comment on Issue #250 some words in NVDA are starting to speak incorrectly since the last espeak NG update for it
By derekriemer:

open might be one too, but I bet this is a different phoneme. It sounds like a person who got hit in the mouth and has a fat lip when espeak-ng says the p in open (The p is muted and sort of has a v embedded in the p).

Pull Request Opened #github

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

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

#249 emscripten/Makefile support for both Linux, macOS

I added a test to support compilation of JS on macOS alongside on Linux, as detailed in discussion of issue #243 ( https://github.com/espeak-ng/espeak-ng/issues/243#issuecomment-298897646 )

Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #243 Failing to compile espeak-ng.js with emscripten under MacOS
By pettarin:

OK, no problem.

The fact that emscripten tries to be a "drop-in" replacement toolchain (i.e., compilation with clang -> LLVM IR -> JS instead of gcc -> native binary, driven by the same Makefile/configure) makes it prone to "real .o" vs "LLVM IR .o" issues.

This is especially true for eSpeak-ng, since to build the voice data one needs to do the full (native) compilation, and only then the emscripten compilation. I am afraid there is no real solution other than make clean or emmake make clean.

With respect to the .so vs .dylib issue:

Ideally the "inner" emscripten/Makefile should be generated by the top ./configure script, but these days I am a bit short on time to venture myself in this.

A quicker workaround might be testing for .so vs .dylib existence in the emscripten/Makefile, and act accordingly. I will give this second route a shot later this week. If not successful, I will just add a note for macOS users in the emscripten/README, warning them to manually add the symbolic link.

AP

On 05/01/2017 11:36 PM, Ben Talagan Babut wrote: > I am a bit confused about why you get the error in step 5, rather than > in step 6 --- the latter I would understand better, since the > emscripten/Makefile explicitly references > > Sorry this is my mistake, you're totally right! I've probably messed up > having multiple tabs opened (the step count has changed in your repo). > My remarks about step 5 actually concern step 6. > > BTW, always make sure you |make clean| or |emmake make clean| before > the compilation --- I have wasted a lot of attempts due to emscripten > failing to recognize that e.g. .o files were not LLVM IR files but > actual object files from a previous compilation (with gcc, not with > emscripten)... > > This is absolutely true, I get these kind of errors on .o files too on > your step 5 for example (to get rid of them, a |emmake make clean| is > necessary before |emmake make src/libespeak-ng.la|). The other warnings > I get are at the end of |emmake make| phases on CCLD steps : > > CCLD src/libespeak-ng.la > WARNING:rootDynamic libraries (.so, .dylib, .dll) are currently not supported by Emscripten. For build system emulation purposes, Emscripten will now generate a static library file (.bc) with the suffix '.dylib'. For best practices, please adapt your build system to directly generate a static LLVM bitcode library by setting the output suffix to '.bc.') > > I believe your solution of updating the README is very acceptable atm, > since it makes that issue non-blocking anymore (except that small > dylib/so pb). Many thanks for your help, it is awesome! > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/espeak-ng/espeak-ng/issues/243#issuecomment-298439478, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AD5ZkwJdqstJNrBw7USh6NdJGkMCHRHMks5r1lB7gaJpZM4M-k2M. >


[espeak-ng:master] New Comment on Pull Request #248 Fix Issue #243
By pettarin:

Thank you.

On 05/02/2017 08:53 AM, Reece H. Dunn wrote: > Merged #248 https://github.com/espeak-ng/espeak-ng/pull/248. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/espeak-ng/espeak-ng/pull/248#event-1064977616, or > mute the thread > https://github.com/notifications/unsubscribe-auth/AD5ZkyJR_pLKwQduzlpVkhVBrUTHyk2Wks5r1tLWgaJpZM4NNWKT. >

Github push to espeak-ng:espeak-ng #github

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

5 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
9af96da469b8: Make the encoding.h API public.

Added: src/include/espeak-ng/encoding.h
Removed: src/libespeak-ng/encoding.h
Modified: src/include/espeak-ng/espeak_ng.h
Modified: src/libespeak-ng/compiledict.c
Modified: src/libespeak-ng/dictionary.c
Modified: src/libespeak-ng/encoding.c
Modified: src/libespeak-ng/espeak_api.c
Modified: src/libespeak-ng/intonation.c
Modified: src/libespeak-ng/numbers.c
Modified: src/libespeak-ng/phonemelist.c
Modified: src/libespeak-ng/readclause.c
Modified: src/libespeak-ng/setlengths.c
Modified: src/libespeak-ng/speech.c
Modified: src/libespeak-ng/synth_mbrola.c
Modified: src/libespeak-ng/synthdata.c
Modified: src/libespeak-ng/synthesize.c
Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tr_languages.c
Modified: src/libespeak-ng/translate.c
Modified: src/libespeak-ng/voices.c
Modified: tests/encoding.c
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
683579f4030c: Make the tokenizer.h API public.

Added: src/include/espeak-ng/tokenizer.h
Removed: src/libespeak-ng/tokenizer.h
Modified: src/libespeak-ng/tokenizer.c
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
0705844bf884: tokenizer.c: Move general category classification that does not override property behaviour to the end, for generic classification.

Modified: src/libespeak-ng/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
786575c6ed7c: tokenizer.c: Support general punctuation tokens.

Modified: src/include/espeak-ng/tokenizer.h
Modified: src/libespeak-ng/tokenizer.c
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
dd90d3812d1f: tokenizer.c: Support general symbol tokens.

Modified: src/include/espeak-ng/tokenizer.h
Modified: src/libespeak-ng/tokenizer.c
Modified: tests/tokenizer.c

Updates to Github #github

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

15 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
a902f451d875: tests/tokenizer.test: Support printing the tokens from a provided file, making it easy to investigate tokenizer issues.

Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
d50f3f2fa575: tokenizer.c: Support word tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By chrislm <llajta2012@...>:
5d8bb74169cb: IT: new improvements tested on april 2017 reduced length to 160 for unstressed syllables Added some exceptions to the italian dictionaries

Modified: dictsource/it_list
Modified: dictsource/it_listx
Modified: src/libespeak-ng/tr_languages.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
0bbc9e9730ca: Merge remote-tracking branch 'Christianlm/master'

Modified: dictsource/it_list
Modified: dictsource/it_listx
Modified: src/libespeak-ng/tr_languages.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
8f62e183244b: tokenizer.c: Support full stop tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
128ceaff6a01: tokenizer.c: Support question mark tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
c9199cfacb73: tokenizer.c: Support exclamation mark tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
7560070dcd7b: tokenizer.c: Support comma tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
af7e8fc5a370: tokenizer.c: Support colon tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By Alberto Pettarin <alberto@...>:
6ce74efeca23: Fixed selection of default voice in JS demo

Modified: emscripten/js/demo.js


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
b847df63b554: tokenizer.c: Support semicolon tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


[espeak-ng:master] By Alberto Pettarin <alberto@...>:
123309a07bd1: Added git ignore for emscripted in UCD tools

Modified: src/ucd-tools/.gitignore


[espeak-ng:master] By Alberto Pettarin <alberto@...>:
3b4487e8a730: Updated directions to compile JS with emscripten

Modified: emscripten/README.md


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
706e780ff4ed: Merge remote-tracking branch 'pettarin/master'

Modified: emscripten/README.md
Modified: emscripten/js/demo.js
Modified: src/ucd-tools/.gitignore


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
55bfbb475425: tokenizer.c: Support ellipsis tokens.

Modified: src/libespeak-ng/tokenizer.c
Modified: src/libespeak-ng/tokenizer.h
Modified: tests/tokenizer.c


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

#247 IT: new improvements tested on april 2017

reduced length to 160 for unstressed syllables

Added some exceptions to the italian dictionaries


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

#248 Fix Issue #243

Fix Issue #243 by updating the directions to compile the JS worker with emscripten.

[espeak-ng:master] reported: Failing to compile espeak-ng.js with emscripten under MacOS #github

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

[espeak-ng:master] New Comment on Issue #243 Failing to compile espeak-ng.js with emscripten under MacOS
By BenTalagan:

I am a bit confused about why you get the error in step 5, rather than in step 6 --- the latter I would understand better, since the emscripten/Makefile explicitly references

Sorry this is my mistake, you're totally right! I've probably messed up having multiple tabs opened (the step count has changed in your repo). My remarks about step 5 actually concern step 6.

BTW, always make sure you make clean or emmake make clean before the compilation --- I have wasted a lot of attempts due to emscripten failing to recognize that e.g. .o files were not LLVM IR files but actual object files from a previous compilation (with gcc, not with emscripten)...

This is absolutely true, I get these kind of errors on .o files too on your step 5 for example (to get rid of them, a emmake make clean is necessary before emmake make src/libespeak-ng.la). The other warnings I get are at the end of emmake make phases on CCLD steps :

CCLD     src/libespeak-ng.la
WARNING:rootDynamic libraries (.so, .dylib, .dll) are currently not supported by Emscripten. For build system emulation purposes, Emscripten will now generate a static library file (.bc) with the suffix '.dylib'. For best practices, please adapt your build system to directly generate a static LLVM bitcode library by setting the output suffix to '.bc.')

I believe your solution of updating the README is very acceptable atm, since it makes that issue non-blocking anymore (except that small dylib/so pb). Many thanks for your help, it is awesome!

[espeak-ng:master] reported: Failing to compile espeak-ng.js with emscripten under MacOS #github

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

[espeak-ng:master] New Comment on Issue #243 Failing to compile espeak-ng.js with emscripten under MacOS
By pettarin:

Hi, I forgot to mention that the new compilation flow (i.e., compiling UCD tools before the final target) has been tested on Linux, in the sense that eventually I get the worker and data JS files as expected on my laptop running Debian.

Yes, a few warnings are output, but you can safely ignore them. (Details below)

I am a bit confused about why you get the error in step 5, rather than in step 6 --- the latter I would understand better, since the emscripten/Makefile explicitly references

EM_LIBESPEAKNG_SO=../src/.libs/libespeak-ng.so

which seems to have .dylib extension on macOS. Probably the easiest approach is for me to check on my Mac Mini one of the next days.

BTW, always make sure you make clean or emmake make clean before the compilation --- I have wasted a lot of attempts due to emscripten failing to recognize that e.g. .o files were not LLVM IR files but actual object files from a previous compilation (with gcc, not with emscripten)...

AP

  • About the warnings: two or three are generated by clang (but not by gcc), and I will report them separately, as they are relevant for espeak-ng per se. Then, there are warnings generated by emscripten when compiling UCD tests, and you can ignore them for sure. Finally, there is a warning about ieee80, generated by emscripten in the libespeak-ng.la pass, that I have not investigated yet. Anyway, the JS files are output (at least on Linux) and they work as expected, so I guess this latter warning can be safely ignored as well.

On 05/01/2017 10:40 PM, Ben Talagan Babut wrote: > Hi @pettarin https://github.com/pettarin and many thanks for your time > and patience ! > > I've tried to compiled from a checkout of your current repo, and it > failed at step 5 (I had a few warnings before but they do not seem > critical). > > Midgaard:emscripten ben$ emmake make > make: *** No rule to make target ../src/.libs/libespeak-ng.so', needed byjs/espeakng.worker.js'. Stop. > > This is the content of my ../src/.libs before step 5 : > > Midgaard:.libs ben$ ls -lat > total 2992 > drwxr-xr-x 7 ben staff 238 1 mai 22:29 . > drwxr-xr-x 15 ben staff 510 1 mai 22:14 .. > -rw-r--r-- 1 ben staff 749380 1 mai 22:14 libespeak-ng.1.dylib > -rw-r--r-- 1 ben staff 769016 1 mai 22:14 libespeak-ng.a > lrwxr-xr-x 1 ben staff 20 1 mai 22:14 libespeak-ng.dylib -> libespeak-ng.1.dylib > lrwxr-xr-x 1 ben staff 18 1 mai 22:14 libespeak-ng.la -> ../libespeak-ng.la > -rw-r--r-- 1 ben staff 954 1 mai 22:14 libespeak-ng.lai > > However, creating the following link will allow to finish the build > process : > > ln -s libespeak-ng.a libespeak-ng.so > > It seems to me a bit hacky, and maybe it's because there are some steps > in the process which are not done the clean way? (That'd explain it is > so complicated to emcompile on MacOS...). > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/espeak-ng/espeak-ng/issues/243#issuecomment-298426645, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AD5Zkxsr4JUfFYaLwtMzPksOrPz8whkFks5r1kNBgaJpZM4M-k2M. >

[espeak-ng:master] reported: Failing to compile espeak-ng.js with emscripten under MacOS #github

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

[espeak-ng:master] New Comment on Issue #243 Failing to compile espeak-ng.js with emscripten under MacOS
By BenTalagan:

Hi @pettarin and many thanks for your time and patience !

I've tried to compiled from a checkout of your current repo, and it failed at step 5 (I had a few warnings before but they do not seem critical).

Midgaard:emscripten ben$ emmake make
make: *** No rule to make target `../src/.libs/libespeak-ng.so', needed by `js/espeakng.worker.js'.  Stop.

This is the content of my ../src/.libs before step 5 :

Midgaard.libs ben$ ls -lat
total 2992
drwxr-xr-x   7 ben  staff     238  1 mai 22:29 .
drwxr-xr-x  15 ben  staff     510  1 mai 22:14 ..
-rw-r--r--   1 ben  staff  749380  1 mai 22:14 libespeak-ng.1.dylib
-rw-r--r--   1 ben  staff  769016  1 mai 22:14 libespeak-ng.a
lrwxr-xr-x   1 ben  staff      20  1 mai 22:14 libespeak-ng.dylib -> libespeak-ng.1.dylib
lrwxr-xr-x   1 ben  staff      18  1 mai 22:14 libespeak-ng.la -> ../libespeak-ng.la
-rw-r--r--   1 ben  staff     954  1 mai 22:14 libespeak-ng.lai

However, creating the following link will allow to finish the build process : shell ln -s libespeak-ng.a libespeak-ng.so It seems to me a bit hacky, and maybe it's because there are some steps in the process which are not done the clean way? (That'd explain it is so complicated to emcompile on MacOS...).

[espeak-ng:master] reported: Failing to compile espeak-ng.js with emscripten under MacOS #github

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

[espeak-ng:master] New Comment on Issue #243 Failing to compile espeak-ng.js with emscripten under MacOS
By pettarin:

@BenTalagan I have opened PR #248 which updates the directions to compile the JS worker.

Basically, the UCD tools should be compiled to JS with emscripten, before compiling to JS the entire espeak-ng library (still with emscripten).

For now, I have just added the relevant step to the directions to the emscripten/README file. The optimal solution, however, would be figuring out whether this intermediate step (compiling UCD tools to JS) can be done automatically, e.g. by modifying the top/root Makefile.am --- but I am not a make&friends expert, so for now I am happy with just knowing with an extra manual step.

Pull Request Opened #github

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

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

#248 Fix Issue #243

Fix Issue #243 by updating the directions to compile the JS worker with emscripten.