Date   
Pull Request Opened #github

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

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

#588 Modify Vietnamese phoneme rules and tone

Updates to Github #github

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

7 New Commits:

[espeak-ng:master] By Anh Hoang Nguyen <hoanganhA91013@...>:
a3865a54b00f: vi: modify Vietnamese phoneme rules and tone

Modified: dictsource/vi_list
Modified: dictsource/vi_rules
Modified: espeak-ng-data/lang/aav/vi
Modified: phsource/envelopes.png
Modified: phsource/ph_vietnam


[espeak-ng:master] By Anh Hoang Nguyen <hoanganhA91013@...>:
7239b8a37a7b: vi: add rules for aN and ac

Modified: phsource/ph_vietnam


[espeak-ng:master] By Anh Hoang Nguyen <hoanganhA91013@...>:
ab7fdd5b5d87: vi: increase length of dipthongs

Modified: phsource/ph_vietnam


[espeak-ng:master] By Anh Hoang Nguyen <hoanganhA91013@...>:
b6c5680ba4e6: vi: modify rule for qu

Modified: dictsource/vi_rules


[espeak-ng:master] By Anh Hoang Nguyen <hoanganhA91013@...>:
60a6015b717f: vi: add rules for .group c

Modified: dictsource/vi_rules


[espeak-ng:master] By Anh Hoang Nguyen <hoanganhA91013@...>:
2544d2fddd73: vi: modify length for vowels

Modified: phsource/ph_vietnam


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
8356a182a9eb: vi: update language pronunciation test

Modified: tests/language-pronunciation.test


1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
18c91eeb2973: vi: update changelog

Modified: CHANGELOG.md

Updates to Github #github

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

[espeak-ng:master] New Comment on Pull Request #588 Modify Vietnamese phoneme rules and tone
By valdisvi:

Thanks for contribution! Your changes are included in master as separate commits instead of automatic merge because: 1. Merged branches make bisection harder and (I don't like merging messages generated for automatic merges in GitHub). 2. I squashed three forward-and-backward vowel modifications in one commit, and also added prefix "vi: " in message to highlight changed language better. It will be nice, if you will follow this message convention in future. 3. I added another change 8356a18 for automated pronunciation changes due do changed pronunciation rules. (that is why All checks have failed message appeared in your pull request status). In future you can check this with make check command and adjust tests appropriately yourself.


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

#588 Modify Vietnamese phoneme rules and tone


[espeak-ng:master] New Comment on Pull Request #588 Modify Vietnamese phoneme rules and tone
By valdisvi:

Thanks for contribution! Your changes are included in master as separate commits instead of automatic merge because: 1. Merged branches make bisection harder and (I don't like merging messages generated for automatic merges in GitHub). 2. I squashed three forward-and-backward vowel modifications in one commit, and also added prefix "vi: " in message to highlight changed language better. It will be nice, if you will follow this message convention in future. 3. I added another change 8356a18 for automated pronunciation changes due do changed pronunciation rules (that is why All checks have failed message appeared in your pull request status). In future you can check this with make check command and adjust tests appropriately yourself.


1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
b8baa1e6cd9d: ur: updates from Ejaz Shah

Modified: dictsource/ur_list
Modified: dictsource/ur_rules

Re: Improvements for Urdu

Valdis Vitolins
 

Thanks for contribution!

Your changes are included in this commit:
https://github.com/espeak-ng/espeak-ng/commit/b8baa1e6cd9dfa262687b68fd
713e1edfb96de5b

Note that your files had Byte order mark at the beginning of the file
https://en.wikipedia.org/wiki/Byte_order_mark

I removed it myself, because it may break/confuse some tools (mostly
simply written scripts). You should check, how to configure your (or
choose proper) editor to not put it in file.

Valdis

Hello,


Some more pronunciation changes for Urdu in the attached dictionary 
files. I hope these can be included in eSpeak-ng.



[espeak-ng:master] reported: Added Pyash constructed language to eSpeak #github

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

[espeak-ng:master] New Comment on Pull Request #533 Added Pyash constructed language to eSpeak
By valdisvi:

Hi, @elspru! I hesitate to include your pull request because: 1. Puash language seems just made up by you, because I couldn't find any reliable resource about it. Can you provide reliable information that this language is recognized and has correct code for it. 2. Changes in configuration files seems inconsistent, language code is sometimes shortened as puac, sometimes as puash and there are also references to lobjan, which is different language (which has entry in wikipedia though).

[espeak-ng:master] new issue: Getting phoneme features #github

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

[espeak-ng:master] New Issue Created by Shaul1321:
#589 Getting phoneme features

Hi,

The page "Phoneme Features and the International Phonetic Alphabet" describes the schema supported by eSpeak. However, it's not cleat to me what command to run to actually get the features for a given word in (say) Italian or Latin. I'd appreciate your help.

Updates to Github #github

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

[espeak-ng:master] New Issue Created by Shaul1321:
#589 Getting phoneme features

Hi,

The page "Phoneme Features and the International Phonetic Alphabet" describes the schema supported by eSpeak. However, it's not cleat to me what command to run to actually get (as a string) the features for a given word in (say) Italian or Latin, for a specific scheme. I'd appreciate your help.


[espeak-ng:master] New Issue Created by Shaul1321:
#589 Getting phoneme features

Hi,

The page "Phoneme Features and the International Phonetic Alphabet" describes the schema supported by eSpeak. However, it's not cleat to me what command to run to actually get (as a string) the phonological features for a given word in (say) Italian or Latin, for a specific scheme. I'd appreciate your help.

Pull Request Opened #github

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

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

#590 German: Fixed some more pronunciation errors

Pull Request Updated #github

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

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

#590 German: Fixed some more pronunciation errors

Pull Request Opened #github

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

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

#591 vi: modify rules for c, k and q

Pull Request Opened #github

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

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

#592 vi: add new phoneme k

Pull Request Updated #github

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

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

#592 vi: add new phoneme k

Pull Request Updated #github

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

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

#592 vi: add new phoneme k

mis spoken word

Travis Siegel
 

I noticed today when proofreading a document that espeak (I'm using the ivan voice) says wichita (which is a city in Kansas I believe) as if it ended in an r.

It says it as if it were spelled

witchitar.  I find this very strange, and interestingly enough, I've run across this kind of behavior before.  I don't know why it would do this, but if anyone has the capability to figure it out, it may lead to fixing several mispronunciations.

Re: mis spoken word

Valdis Vitolins
 

Pronunciation for Wichita is set explicitly in pronunciation file:

https://github.com/espeak-ng/espeak-ng/blob/master/dictsource/en_list#L
4451

Therefore (I assume), it is correct pronunciation for UK English.

What you think should be correct pronunciation for (I assume) US
English?

Valdis

I noticed today when proofreading a document that espeak (I'm using
the 
ivan voice) says wichita (which is a city in Kansas I believe) as if
it 
ended in an r.

It says it as if it were spelled

witchitar.  I find this very strange, and interestingly enough, I've
run 
across this kind of behavior before.  I don't know why it would do
this, 
but if anyone has the capability to figure it out, it may lead to
fixing 
several mispronunciations.




Re: mis spoken word

Karl Eick
 

Fairly simple, use A: instead of a@

Karl
Am 05.03.2019 um 21:28 schrieb Valdis Vitolins via Groups.Io:

Pronunciation for Wichita is set explicitly in pronunciation file:

https://github.com/espeak-ng/espeak-ng/blob/master/dictsource/en_list#L
4451

Therefore (I assume), it is correct pronunciation for UK English.

What you think should be correct pronunciation for (I assume) US
English?

Valdis

I noticed today when proofreading a document that espeak (I'm using
the
ivan voice) says wichita (which is a city in Kansas I believe) as if
it
ended in an r.

It says it as if it were spelled

witchitar.  I find this very strange, and interestingly enough, I've
run
across this kind of behavior before.  I don't know why it would do
this,
but if anyone has the capability to figure it out, it may lead to
fixing
several mispronunciations.




Pull Request Updated #github

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

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

#590 German: Fixed some more pronunciation errors

Re: mis spoken word

Travis Siegel
 

Yeah, that's the word alright, but I can't figure out how to read the pronunciation it's supposed to have.  If it helps, the word should be pronounced like witch then a short i as in iguana, then a ta ending like tah (same as utah).  Not sure why it would require a special entry in the dictionary, I don't know how to remove entries from the dictionary myself, or I'd try that and see how it pronounces it on its own, but sounding like an r is at the end of it certainly isn't correct.

On 3/5/2019 3:28 PM, Valdis Vitolins via Groups.Io wrote:
Pronunciation for Wichita is set explicitly in pronunciation file:

https://github.com/espeak-ng/espeak-ng/blob/master/dictsource/en_list#L
4451

Therefore (I assume), it is correct pronunciation for UK English.

What you think should be correct pronunciation for (I assume) US
English?

Valdis

I noticed today when proofreading a document that espeak (I'm using
the
ivan voice) says wichita (which is a city in Kansas I believe) as if
it
ended in an r.

It says it as if it were spelled

witchitar.  I find this very strange, and interestingly enough, I've
run
across this kind of behavior before.  I don't know why it would do
this,
but if anyone has the capability to figure it out, it may lead to
fixing
several mispronunciations.




Re: mis spoken word

Karl Eick
 

Hi,

Removing it completely causes a different, wrong pronunciation
altogether. I suggest that little change I mentioned in my previous
mail. Currently the entry is made like this:

Wichita        wItSI#tA@

This should be changed to:

Wichita        wItSI#tA:
To make the US English voice pronounce it right.


Karl

Am 06.03.2019 um 00:04 schrieb Travis Siegel:

Yeah, that's the word alright, but I can't figure out how to read the
pronunciation it's supposed to have.  If it helps, the word should be
pronounced like witch then a short i as in iguana, then a ta ending
like tah (same as utah).  Not sure why it would require a special
entry in the dictionary, I don't know how to remove entries from the
dictionary myself, or I'd try that and see how it pronounces it on its
own, but sounding like an r is at the end of it certainly isn't correct.

On 3/5/2019 3:28 PM, Valdis Vitolins via Groups.Io wrote:
Pronunciation for Wichita is set explicitly in pronunciation file:

https://github.com/espeak-ng/espeak-ng/blob/master/dictsource/en_list#L
4451

Therefore (I assume), it is correct pronunciation for UK English.

What you think should be correct pronunciation for (I assume) US
English?

Valdis

I noticed today when proofreading a document that espeak (I'm using
the
ivan voice) says wichita (which is a city in Kansas I believe) as if
it
ended in an r.

It says it as if it were spelled

witchitar.  I find this very strange, and interestingly enough, I've
run
across this kind of behavior before.  I don't know why it would do
this,
but if anyone has the capability to figure it out, it may lead to
fixing
several mispronunciations.






Pull Request Updated #github

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

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

#592 vi: add new phoneme k