Date   
FW: [espeak-ng] concerning the new version of Espeak FW: new version of nvda

Katty Geltmeyer <kattygeltmeyer@...>
 

Dear

 

see below, the mail I sent earlier: the issues I tried to describe/report are still occurring in nvda.2017.4

ch and g in Dutch and log are nearly pronounced as an f but deformed; I even can't describe.

Language: =Dutch,

voice =max.

 

Sincerely, Katty

Van: espeak-ng@groups.io [mailto:espeak-ng@groups.io] Namens Katty Geltmeyer
Verzonden: woensdag 29 november 2017 12:56
Aan: es
peak-ng@groups.io
Onderwerp: [espeak-ng] concerning the new version of Espeak FW: new version of nvda

 

Dear

 

I forward a message (see below) that is describing some issues with Espeak ng

 

Problem:

I remark that a problem is occurring since I use nvda.2017.4rc2:

when I type Dutch espeak sounds deformed the ch ; idem problem with g of log. Listen how log and Dutch are pronounced, it's strangely how the ch and g are pronounced.

 

Info I got from mail below:

although between 2017.3 and 2017.4 we upgraded the build of eSpeak NG we use to 1.49.2, so maybe something between 1.49.1 and .2 (we updated to 1.49.1 in 2017.3, …

 

Chosen language =Dutch, voice =Max.

 

Could this please be solved soon? The quality of speech is decreasing instead of improving.

 

Thanks in advance.

 

Sincerely, Katty

Van: Quentin Christensen [mailto:quentin@...]
Verzonden: woensdag 29 november 2017 0:51
Aan: Katty Geltmeyer <kattygeltmeyer@...>
Onderwerp: Re: new version of nvda

 

Hi Katty,

 

It looks like an issue with eSpeak NG.  I found a comment on this GitHub thread on eSpeak NG's repository which references it lightly: https://github.com/espeak-ng/espeak-ng/issues/65

 

That doesn't look like anything that has changed recently though, although between 2017.3 and 2017.4 we upgraded the build of eSpeak NG we use to 1.49.2, so maybe something between 1.49.1 and .2 (we updated to 1.49.1 in 2017.3, we are trying to keep more up to date on eSpeak NG builds).

 

When I did a search for "dutch" on the eSpeak NG issues, I found four: https://github.com/espeak-ng/espeak-ng/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+dutch

 

Regards

 

Quentin.

 

On Tue, Nov 28, 2017 at 9:49 PM, Katty Geltmeyer <kattygeltmeyer@...> wrote:

addition: I found out this issue at the 10th of november. Perhaps I found it out earlier, but at that date I sent my first message to a Dutch group of nvda users about this issue.

Best, Katty

 

Van: Quentin Christensen [mailto:quentin@...]
Verzonden: dinsdag 28 november 2017 11:37


Aan: Katty Geltmeyer <kattygeltmeyer@...>
Onderwerp: Re: new version of nvda

 

Hi Katty,

 

You say "still there", did this problem exist in 2017.3? (just to work out whether it is a new issue, or if it had previously existed)

 

Kind regards

 

Quentin.

 

On Tue, Nov 28, 2017 at 9:35 PM, Katty Geltmeyer <kattygeltmeyer@...> wrote:

I remark that a problem is still there: when I type Dutch espeak sounds deformed the ch ; idem problem with g of log. Listen how log and Dutch are pronounced, it's strangely how the ch and g are pronounced.

 

Best, Katty

 

Van: Quentin Christensen [mailto:quentin@...]
Verzonden: dinsdag 28 november 2017 11:09
Aan: Katty Geltmeyer <kattygeltmeyer@...>
Onderwerp: Re: new version of nvda

 

Hi Katty,

 

There will be an RC3, but I don't think it's out yet.  In the meantime, here is RC2 (read the "What's new" in the help menu for all the changes): https://www.nvaccess.org/post/nvda2017-4rc2released/

 

Kind regards

 

Quentin.

 

On Tue, Nov 28, 2017 at 7:23 PM, Katty Geltmeyer <kattygeltmeyer@...> wrote:

Hi Quentin

 

Is there a beta or rc version of the new nvda I can test? If yes, could you send me the link?

 

Thanks in advance.

 

Best, Katty

 

------------------

https://google.com/+KattyGeltmeyer

http://kattykrabbelt.blogspot.com/feeds/posts/default

 



 

--

Quentin Christensen
Training and Support Manager

 

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 

Pull Request Opened #github

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

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

#349 Add mbrola support for arabic

Add ar1 mbrola support Modify ar2 mbrola support

Re: Espeak-ng packaged with NVDA 2017.4

Karl Eick
 

Hi,

The hundred thing only applies to the word, not the number. That could be made more consistent. Allso, I would remove that velarization used for the n in US english.

Regards,

Karl Eick


Am 07.12.2017 um 11:29 schrieb Sharni-Lee Ward:

I appreciate the lesson on why things sound like they did, but I was happy with the way espeak handled things like "in case" and "one game" before these changes.


As for "for the", it sounds almost like "further" said faster. The four part is over-emphasised. "For a" sounds more like "fer a" to me and it's just ... UGH. I liked how those were done before and I don't know why that was changed.


To end on a somewhat positive note, I do like the improvements to "also" and all words that contain "muse". It's nice to hear that sounding right.
On 7/12/2017 6:30 PM, Reece H. Dunn wrote:
On Wed, Dec 6, 2017 at 04:45 pm, Sharni-Lee Ward wrote:
Also, words that end with n or an n sound that are followed by words
that start with a hard c or g sound like the two words were smushed
together. Something like "in games" being pronounced like "ing games".
That's ... not how English works...
That's a feature of English called velarization. Try saying "in games" without the middle of your tongue pressing up against the velum (the large ridge behind our mouth) on the "n" sound -- this happens because your tongue is moving in position to sound the hard k/g sound, and thus the n sound gets influenced by this. This is why words like king and sing, and words ending in "ing" use that sound.

NOTE: Accents that don't pronounce the 'g' in -ing words (e.g. nothin') don't have the velarization due to not pronouncing the 'g'. Other accents have the velarization of the 'n', but don't sound the release part of the 'g'. Other accents that pronounce -ing like -ink (e.g. nothink) pronounce the 'n' with the back of their tongue in a glottal stop, so the 'n' does not get velarized in that case.

On 7/12/2017 11:38 AM, Sharni-Lee Ward wrote:
Hi,


I use the English setting now known as "English Great Britain" in
Espeak-ng. When I updated to the latest version of NVDA, the new version
of espeak-ng packaged with it sounded strange. Phrases like "for the"
and "for a" sound really weird.
How so?

Numbers like "twenty" and "ninety" sound just a tad slower than they did before.
Is that at the end of the word? That is the only part that has changed.

Words like "percent" and its
derivatives, which were pronounced just fine before, now sound off
because of the lack of emphasis on the second syllable.
That's a bug. Thanks for the report.

I can handle the
changed pronunciation of "because", but the one for "hundred" doesn't
sound quite right.
Both are valid English pronunciations, but my intention is to make that accent closer to what you are expecting, so needs adjusting.

I've watched a lot of British TV—I know that's not
how they say that, and again, it was pronounced just fine before.
It depends on the accent of the people you have watched. That depends on:
1.  their country and language of origin (e.g. speaking with a German or Irish accent);
2.  the part of England they grew up in (their broad regional accent);
3.  their age (accounting for any accent drift);
4.  their social and educational background (do they have a posher, more RP-like accent? do they have a more urban accent?);
5.  etc.

Why these changes? What prompted them?
The espeak pronunciation rules were inconsistent in how it transcribed various words (see https://github.com/espeak-ng/espeak-ng/blob/master/docs/languages/gmw/en.md). I have also applied pronunciation fixes for several words.

I need to make some adjustments to the voices to reflect my intent of the accents, which should address most of the issues you have (I'm not sure what the problem is with 'for a'). Longer term, I want to make this more flexible and configurable.

Thanks for the feedback,
- Reece


[espeak-ng:master] reported: Bug around Chinese Mandarin in Espeak has been discovered #github

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

[espeak-ng:master] New Comment on Issue #348 Bug around Chinese Mandarin in Espeak has been discovered
By valdisvi:

I fixed list of languages on the test page. I don't know about NVDA, but invoking espeak-ng in command line, cmn or zh-cmn, and yue or zh-yue work as synonyms for voice parameters:

$ espeak-ng -x -vcmn "铁人麝香:从特斯拉到太空探索"
 th'iE21_| z.'@35n_| s.'o-51_| S;'iA55N_|
 tsh'ong35_| th'@51_| s'i[55_| l'A55_| t'Au51_| th'ai51_| kh'ong55_| th'a51n_| s'uo214_|

$ espeak-ng -x -vzh-cmn "铁人麝香:从特斯拉到太空探索"
 th'iE21_| z.'@35n_| s.'o-51_| S;'iA55N_|
 tsh'ong35_| th'@51_| s'i[55_| l'A55_| t'Au51_| th'ai51_| kh'ong55_| th'a51n_| s'uo214_|

$ espeak-ng -x -vyue "铁人麝香:从特斯拉到太空探索"
 t'i3t_| j'a4n_| s'e6_| h'oeng1_|
 c'ung4_| d'a6k_| s'i1_| l'aai1_| d'ou3_| t'aai3_| h'ung1_| t'aa3m_| s'o3k_|

$ espeak-ng -x -vzh-yue "铁人麝香:从特斯拉到太空探索"
 t'i3t_| j'a4n_| s'e6_| h'oeng1_|
 c'ung4_| d'a6k_| s'i1_| l'aai1_| d'ou3_| t'aai3_| h'ung1_| t'aa3m_| s'o3k_|

Re: Espeak-ng packaged with NVDA 2017.4

Sharni-Lee Ward
 

Found another rather egregious one. The "resign" part of "resignedly" is pronounced "Rezeen". I think something went wonky with the suffix "edly".


On 7/12/2017 9:29 PM, Sharni-Lee Ward wrote:

I appreciate the lesson on why things sound like they did, but I was happy with the way espeak handled things like "in case" and "one game" before these changes.


As for "for the", it sounds almost like "further" said faster. The four part is over-emphasised. "For a" sounds more like "fer a" to me and it's just ... UGH. I liked how those were done before and I don't know why that was changed.


To end on a somewhat positive note, I do like the improvements to "also" and all words that contain "muse". It's nice to hear that sounding right.
On 7/12/2017 6:30 PM, Reece H. Dunn wrote:
On Wed, Dec 6, 2017 at 04:45 pm, Sharni-Lee Ward wrote:
Also, words that end with n or an n sound that are followed by words
that start with a hard c or g sound like the two words were smushed
together. Something like "in games" being pronounced like "ing games".
That's ... not how English works...
That's a feature of English called velarization. Try saying "in games" without the middle of your tongue pressing up against the velum (the large ridge behind our mouth) on the "n" sound -- this happens because your tongue is moving in position to sound the hard k/g sound, and thus the n sound gets influenced by this. This is why words like king and sing, and words ending in "ing" use that sound.

NOTE: Accents that don't pronounce the 'g' in -ing words (e.g. nothin') don't have the velarization due to not pronouncing the 'g'. Other accents have the velarization of the 'n', but don't sound the release part of the 'g'. Other accents that pronounce -ing like -ink (e.g. nothink) pronounce the 'n' with the back of their tongue in a glottal stop, so the 'n' does not get velarized in that case.

On 7/12/2017 11:38 AM, Sharni-Lee Ward wrote:
Hi,


I use the English setting now known as "English Great Britain" in
Espeak-ng. When I updated to the latest version of NVDA, the new version
of espeak-ng packaged with it sounded strange. Phrases like "for the"
and "for a" sound really weird.
How so?

Numbers like "twenty" and "ninety" sound just a tad slower than they did before.
Is that at the end of the word? That is the only part that has changed.

Words like "percent" and its
derivatives, which were pronounced just fine before, now sound off
because of the lack of emphasis on the second syllable.
That's a bug. Thanks for the report.

I can handle the
changed pronunciation of "because", but the one for "hundred" doesn't
sound quite right.
Both are valid English pronunciations, but my intention is to make that accent closer to what you are expecting, so needs adjusting.

I've watched a lot of British TV—I know that's not
how they say that, and again, it was pronounced just fine before.
It depends on the accent of the people you have watched. That depends on:
1.  their country and language of origin (e.g. speaking with a German or Irish accent);
2.  the part of England they grew up in (their broad regional accent);
3.  their age (accounting for any accent drift);
4.  their social and educational background (do they have a posher, more RP-like accent? do they have a more urban accent?);
5.  etc.

Why these changes? What prompted them?
The espeak pronunciation rules were inconsistent in how it transcribed various words (see https://github.com/espeak-ng/espeak-ng/blob/master/docs/languages/gmw/en.md). I have also applied pronunciation fixes for several words.

I need to make some adjustments to the voices to reflect my intent of the accents, which should address most of the issues you have (I'm not sure what the problem is with 'for a'). Longer term, I want to make this more flexible and configurable.

Thanks for the feedback,
- Reece


Re: Espeak-ng packaged with NVDA 2017.4

Sharni-Lee Ward
 

I appreciate the lesson on why things sound like they did, but I was happy with the way espeak handled things like "in case" and "one game" before these changes.


As for "for the", it sounds almost like "further" said faster. The four part is over-emphasised. "For a" sounds more like "fer a" to me and it's just ... UGH. I liked how those were done before and I don't know why that was changed.


To end on a somewhat positive note, I do like the improvements to "also" and all words that contain "muse". It's nice to hear that sounding right.

On 7/12/2017 6:30 PM, Reece H. Dunn wrote:
On Wed, Dec 6, 2017 at 04:45 pm, Sharni-Lee Ward wrote:
Also, words that end with n or an n sound that are followed by words
that start with a hard c or g sound like the two words were smushed
together. Something like "in games" being pronounced like "ing games".
That's ... not how English works...
That's a feature of English called velarization. Try saying "in games" without the middle of your tongue pressing up against the velum (the large ridge behind our mouth) on the "n" sound -- this happens because your tongue is moving in position to sound the hard k/g sound, and thus the n sound gets influenced by this. This is why words like king and sing, and words ending in "ing" use that sound.

NOTE: Accents that don't pronounce the 'g' in -ing words (e.g. nothin') don't have the velarization due to not pronouncing the 'g'. Other accents have the velarization of the 'n', but don't sound the release part of the 'g'. Other accents that pronounce -ing like -ink (e.g. nothink) pronounce the 'n' with the back of their tongue in a glottal stop, so the 'n' does not get velarized in that case.

On 7/12/2017 11:38 AM, Sharni-Lee Ward wrote:
Hi,


I use the English setting now known as "English Great Britain" in
Espeak-ng. When I updated to the latest version of NVDA, the new version
of espeak-ng packaged with it sounded strange. Phrases like "for the"
and "for a" sound really weird.
How so?

Numbers like "twenty" and "ninety" sound just a tad slower than they did before.
Is that at the end of the word? That is the only part that has changed.

Words like "percent" and its
derivatives, which were pronounced just fine before, now sound off
because of the lack of emphasis on the second syllable.
That's a bug. Thanks for the report.

I can handle the
changed pronunciation of "because", but the one for "hundred" doesn't
sound quite right.
Both are valid English pronunciations, but my intention is to make that accent closer to what you are expecting, so needs adjusting.

I've watched a lot of British TV—I know that's not
how they say that, and again, it was pronounced just fine before.
It depends on the accent of the people you have watched. That depends on:
1.  their country and language of origin (e.g. speaking with a German or Irish accent);
2.  the part of England they grew up in (their broad regional accent);
3.  their age (accounting for any accent drift);
4.  their social and educational background (do they have a posher, more RP-like accent? do they have a more urban accent?);
5.  etc.

Why these changes? What prompted them?
The espeak pronunciation rules were inconsistent in how it transcribed various words (see https://github.com/espeak-ng/espeak-ng/blob/master/docs/languages/gmw/en.md). I have also applied pronunciation fixes for several words.

I need to make some adjustments to the voices to reflect my intent of the accents, which should address most of the issues you have (I'm not sure what the problem is with 'for a'). Longer term, I want to make this more flexible and configurable.

Thanks for the feedback,
- Reece

[espeak-ng:master] new issue: Chinese Mandarin: English words pronunciation problem #github

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

[espeak-ng:master] New Issue Created by surfer0627:
#347 Chinese Mandarin: English words pronunciation problem

Hi, This case occurred in Chinese Mandarin.

Steps to reproduce:

  1. Open testing page.
  2. Choose language Chinese Mandarin.
  3. Type. > English literature

Expected behavior:

ESpeak NG reads English words correctly.

Actual behavior:

It is difficult to understand the pronunciation. Pronunciation English America: 'INglIS l'It#3rI#tS3 Chinese Mandarin: 55Nl'i55s.| l,i55th@55z.,A55thu55z.'o-55

CC: @valdisvi

Re: Espeak-ng packaged with NVDA 2017.4

Reece H. Dunn
 

On Wed, Dec 6, 2017 at 04:45 pm, Sharni-Lee Ward wrote:
Also, words that end with n or an n sound that are followed by words
that start with a hard c or g sound like the two words were smushed
together. Something like "in games" being pronounced like "ing games".
That's ... not how English works...
That's a feature of English called velarization. Try saying "in games" without the middle of your tongue pressing up against the velum (the large ridge behind our mouth) on the "n" sound -- this happens because your tongue is moving in position to sound the hard k/g sound, and thus the n sound gets influenced by this. This is why words like king and sing, and words ending in "ing" use that sound.

NOTE: Accents that don't pronounce the 'g' in -ing words (e.g. nothin') don't have the velarization due to not pronouncing the 'g'. Other accents have the velarization of the 'n', but don't sound the release part of the 'g'. Other accents that pronounce -ing like -ink (e.g. nothink) pronounce the 'n' with the back of their tongue in a glottal stop, so the 'n' does not get velarized in that case.

On 7/12/2017 11:38 AM, Sharni-Lee Ward wrote:
Hi,


I use the English setting now known as "English Great Britain" in
Espeak-ng. When I updated to the latest version of NVDA, the new version
of espeak-ng packaged with it sounded strange. Phrases like "for the"
and "for a" sound really weird.
How so?

Numbers like "twenty" and "ninety" sound just a tad slower than they did before.
Is that at the end of the word? That is the only part that has changed.

Words like "percent" and its
derivatives, which were pronounced just fine before, now sound off
because of the lack of emphasis on the second syllable.
That's a bug. Thanks for the report.

I can handle the
changed pronunciation of "because", but the one for "hundred" doesn't
sound quite right.
Both are valid English pronunciations, but my intention is to make that accent closer to what you are expecting, so needs adjusting.

I've watched a lot of British TV—I know that's not
how they say that, and again, it was pronounced just fine before.
It depends on the accent of the people you have watched. That depends on:
1.  their country and language of origin (e.g. speaking with a German or Irish accent);
2.  the part of England they grew up in (their broad regional accent);
3.  their age (accounting for any accent drift);
4.  their social and educational background (do they have a posher, more RP-like accent? do they have a more urban accent?);
5.  etc.

Why these changes? What prompted them?
The espeak pronunciation rules were inconsistent in how it transcribed various words (see https://github.com/espeak-ng/espeak-ng/blob/master/docs/languages/gmw/en.md). I have also applied pronunciation fixes for several words.

I need to make some adjustments to the voices to reflect my intent of the accents, which should address most of the issues you have (I'm not sure what the problem is with 'for a'). Longer term, I want to make this more flexible and configurable.

Thanks for the feedback,
- Reece

Re: Espeak-ng packaged with NVDA 2017.4

Sharni-Lee Ward
 

Also, words that end with n or an n sound that are followed by words
that start with a hard c or g sound like the two words were smushed
together. Something like "in games" being pronounced like "ing games".
That's ... not how English works...

On 7/12/2017 11:38 AM, Sharni-Lee Ward wrote:
Hi,


I use the English setting now known as "English Great Britain" in
Espeak-ng. When I updated to the latest version of NVDA, the new version
of espeak-ng packaged with it sounded strange. Phrases like "for the"
and "for a" sound really weird. Numbers like "twenty" and "ninety" sound
just a tad slower than they did before. Words like "percent" and its
derivatives, which were pronounced just fine before, now sound off
because of the lack of emphasis on the second syllable. I can handle the
changed pronunciation of "because", but the one for "hundred" doesn't
sound quite right. I've watched a lot of British TV—I know that's not
how they say that, and again, it was pronounced just fine before. Why
these changes? What prompted them?



Espeak-ng packaged with NVDA 2017.4

Sharni-Lee Ward
 

Hi,


I use the English setting now known as "English Great Britain" in
Espeak-ng. When I updated to the latest version of NVDA, the new version
of espeak-ng packaged with it sounded strange. Phrases like "for the"
and "for a" sound really weird. Numbers like "twenty" and "ninety" sound
just a tad slower than they did before. Words like "percent" and its
derivatives, which were pronounced just fine before, now sound off
because of the lack of emphasis on the second syllable. I can handle the
changed pronunciation of "because", but the one for "hundred" doesn't
sound quite right. I've watched a lot of British TV—I know that's not
how they say that, and again, it was pronounced just fine before. Why
these changes? What prompted them?

[espeak-ng:master] reported: Bug around Chinese Mandarin in Espeak has been discovered #github

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

[espeak-ng:master] New Comment on Issue #348 Bug around Chinese Mandarin in Espeak has been discovered
By rhdunn:

NOTE: If they are not removing the previous voice files when copying over the new ones, they may have added duplicate voice entries from changes to the layout of that directory in previous versions of espeak-ng, including the move from the voices directory to the lang directory. In that case, the MBROLA voices and the voice variants are listed in the voices directory, while the languages are in the lang` directory.

Updates to Github #github

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

[espeak-ng:master] Issue #348 Bug around Chinese Mandarin in Espeak has been discovered closed by Giovani93.


[espeak-ng:master] New Comment on Issue #348 Bug around Chinese Mandarin in Espeak has been discovered
By rhdunn:

There is only one instance of each Chinese voice listed by espeak-ng, and via its API:

$ src/espeak-ng --voices | grep Chinese
 5  cmn             --/M      Chinese_(Mandarin) sit/cmn              (zh-cmn 5)(zh 5)
 5  yue             --/M      Chinese_(Cantonese) sit/yue              (zh-yue 5)(zh 8)

Therefore, this is a bug in the odo.lv page and NVDA.


[espeak-ng:master] Label added to issue #348 Bug around Chinese Mandarin in Espeak has been discovered by Giovani93.

Updates to Github #github

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

[espeak-ng:master] New Issue Created by Giovani93:
#348 Bug around Chinese Mandarin in Espeak has been discovered

Hi! I have discovered bug in Mandarin Chinese of Espeak. Here is copy of My e-mail sent to one mailing list. OK, bug is discovered, I think It is misstake of Espeak NG. There are two voices classified, as Mandarin Chinese. One is incorrect and countains bugs. Two voices labelled, as Mandarin Chinese in direction with chinese voices. Please, could You look to this folder and fix the bug? Thank You. Marco


[espeak-ng:master] New Comment on Issue #348 Bug around Chinese Mandarin in Espeak has been discovered
By Giovani93:

Please, test It in this page, there are two Chinese mandarin Espeak and this is not very good for NVDA. http://odo.lv/Espeak?language=en

[espeak-ng:master] new issue: Chinese Mandarin: English words pronunciation problem #github

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

[espeak-ng:master] New Issue Created by surfer0627:
#347 Chinese Mandarin: English words pronunciation problem

Hi, This case occurred in Chinese Mandarin.

Steps to reproduce:

  1. Open testing page.
  2. Choose language Chinese Mandarin.
  3. Type. > English literature

Expected behavior:

ESpeak NG reads English words correctly.

Actual behavior:

It is difficult to understand the pronunciation.

CC: @valdisvi

Updates to Github #github

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

[espeak-ng:master] Label added to issue #346 Big bug in Mandarin Chinese by Giovani93.


[espeak-ng:master] New Comment on Issue #346 Big bug in Mandarin Chinese
By valdisvi:

This is already fixed issue #338 in development version espeak-ng.


[espeak-ng:master] Issue #346 Big bug in Mandarin Chinese closed by Giovani93.


[espeak-ng:master] New Comment on Issue #346 Big bug in Mandarin Chinese
By valdisvi:

This is already fixed issue #338 in development version of espeak-ng.

[espeak-ng:master] new issue: Big bug in Mandarin Chinese #github

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

[espeak-ng:master] New Issue Created by Giovani93:
#346 Big bug in Mandarin Chinese

Hi! I have tested the new Espeak and I have found some bug. Characters in Mandarin Chinese are pronounced, like letter and some kind of number. For example in character for gong luo, character is pronounced as luo yi. I don't know, why. Please, could You fix It? Thank You.

Updates to Github #github

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

2 New Commits:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
4c5499ec04a3: ar: fix definitons of voiced consonats by adding voiced/formant part

Modified: phsource/ph_arabic


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
1d97a1ef935b: ar: issue #186: initial support for mbrola ar2 voice

Added: espeak-ng-data/voices/mb/mb-ar2
Added: phsource/mbrola/ar2
Modified: Makefile.am


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

#345 ar: improvements

Pull Request Opened #github

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

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

#345 ar: improvements

[espeak-ng:master] reported: Why my espeak-ng program doesn't say anything? #github

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

[espeak-ng:master] New Comment on Issue #337 Why my espeak-ng program doesn't say anything?
By valdisvi:

I spend quite much time to get parameters right to compile your example. But after compiling with gcc test.c -lespeak-ng -o test I got it working immediately.

Probably you don't have espeak-data folder or it is in wrong place. If you use Debian packaging guidelines (as well as eSpeakNG insructions), actual folder is /usr/lib/x86_64-linux-gnu/espeak-data, or it could also be /usr/share/espeak-ng-data (and if you use installed version of espeak-ng, one of them could be symbolic link as well as links named espeak-data. /usr/local/share/espeak-ng-data could be used if you build and install it as local application.

Also check, that you don't have issues with pulseaudio.

[espeak-ng:master] reported: Why my espeak-ng program doesn't say anything? #github

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

[espeak-ng:master] New Comment on Issue #337 Why my espeak-ng program doesn't say anything?
By valdisvi:

I spend quite much time to get parameters right to compile your example. But after compiling with gcc test.c -lespeak-ng -o test I got it working immediately.

Probably you don't have espeak-data folder or it is in wrong place. If you use Debian packaging guidelines (as well as eSpeakNG insructions), actual folder is /usr/lib/x86_64-linux-gnu/espeak-data, or it could also be /usr/share/espeak-ng-data (and if you use installed version of espeak-ng, one of them could be symbolic link as well as links named espeak-data. /usr/local/share/espeak-ng-data could be used if you build and install it as local application.