Date   
Re: Updated Dictionary Files for Sindhi and Urdu

Valdis Vitolins
 

Thanks for contribution!

You can review merged changes here:
https://github.com/valdisvi/espeak-ng/commit/669b9f16c2f84d3a6654c2fe82
06b8142642e8de

Valdis

I have made some more changes in the attached sd_list, sd_rules,
ur_list 
and ur_rules. I hope they can be included in eSpeak-ng.



[espeak-ng:master] new issue: Buffer overflow when compiling dictionaries #github

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

[espeak-ng:master] New Issue Created by feerrenrut:
#287 Buffer overflow when compiling dictionaries

Background:

While updating the NVDA espeak-ng submodule to commit fb97d1bd7564c2ff7c305cf7fcbdd29132234846 we have run into some problems compiling the dictionaries. The build system was occasionally halting with a python crash. After some investigation I found that a missing new line at the end of 'ar_listx' was causing a buffer overrun, which I have worked around with https://github.com/nvaccess/espeak-ng/commit/0994206f710a4defc1eecfb78ab70ff57c58fcda.

For this problem (missing new line character); assuming there is no technical reason that a new line character must be present, I suggest that the dictionary compilation is modified to accept files with missing new lines. Otherwise, to save time in debugging and accidental newlines I suggest that a missing newline is detected and reported during dictionary compilation.

There still seems to be a crash or sometimes the process runs indefinitely. Further investigation has led me to find that in LoadDictionary length is sometimes negative. Trying to match up the signed / unsignedness of 'length' (particularly in compile_dictlist_end) I found in some cases it is actually negative when written. On my system I can reliably reproduce this when running through 'compile_dictlist_end()' for the 'bn' dictionary, at hash number 497 we eventually get a length value of -117 (signed) / 4294967179 (unsigned).

I don't really understand how length comes to be -117. I added some asserts (and then built espeak with /SDL /RTC1 /MDd /Od /D_DEBUG MSVC flags) to make debugging this a little easier, see the full diff of espeak: https://github.com/espeak-ng/espeak-ng/compare/master...nvaccessfixEspeakCrashDuringDictCompilation

Also the branch of NVDA that is used to build the fixEspeakCrashDuringDictCompilation is updateEspeak-debugBranch specifically commit: https://github.com/nvaccess/nvda/commit/6bf896248798ee041c034372cc0b18efa5c611dc

Key points:

  • Missing new line at the end of 'ar_listx' causes buffer overrun
  • Signed / unsigned mismatch of length in compile_dictlist_end / LoadDictionary
  • This value appears to be either too large or negative, indicating a problem.

To reproduce locally:

  • On a windows machine (with the required NVDA dependencies)
  • Clone https://github.com/nvaccess/nvda repository
  • Checkout 6bf896248798ee041c034372cc0b18efa5c611dc
  • Build nvda with python scons.py source

Updated Dictionary Files for Sindhi and Urdu

Ejaz Shah
 

I have made some more changes in the attached sd_list, sd_rules, ur_list and ur_rules. I hope they can be included in eSpeak-ng.

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

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

1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
d0169db79294: af: Updates from Christo de Klerk.

Modified: dictsource/af_list
Modified: dictsource/af_rules

Updated Afrikaans dictionary files attached

Christo de Klerk
 

Hi Reece


Here are updated dictionary files for Afrikaans. I have attached af_list, af_rules and a log of the changes I made. As you will see, I made many pronunciation corrections.


Kind regards


Christo

[espeak-ng:master] reported: Typing interrupt doesn't work when using espeakup with espeak-ng #github

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

[espeak-ng:master] New Comment on Issue #285 Typing interrupt doesn't work when using espeakup with espeak-ng
By valdisvi:

espeak-ng allows to use Pulse by default, but particular binary depends on configuration of distributed packages. When I used Pulse with recent espeak-ng versions, I got strange initialization errors. Therefore now I'm using ALSA now.

Re: questions about compilation and publishing of the APK

Valdis Vitolins
 

Hello, Taksan!

Regarding to point #3:

eSpeakNG doesn't have wiki, but editing markdown files is quite close
to it.

The best option would be, if you fork espeak-ng project and then update
README.md file or other *.md files in docs folder (simple edits you can
do directly in browser) and then commit changes and make pull request.

Or for occasional updates you can send comments/patches to this mailing
list and some of us will put them into documentation.

Sincerely,
Valdis Vitolins

Hello everyone, first: Thanks for all the people that make this
project!

Ok now my comments: I compiled the espeak APK for a friend (he needs
it and he is not a developer like me), and now I have these
questions:

1.- Is there any official place to put and/or find compiled APKs? I
will be doing more of these compiles and my friend is not the only
one needing it, others want to try the latest also.

2.- The final step of the wiki is to "sign" the APK. Well, it does
not work for me. Looks like something is wrong with my keys,
something about MDA or SHA1 not correct because the error says
something about the encryption algorithm being wrong. So, I had to
use Android Studio at the end to at least get to a "debug" version of
the APK. Has anybody used that last "sign" command successfully?
exactly as described there? or the encryption algorithm changed but
whe wiki needs updating?

3.- Speaking of the wiki... I had to install and do some extra steps
to make the compilation work in my box (ubuntu). I would like to add
those details and steps I did in the wiki, they are probably very
obvious to whoever wrote the android section of the wiki (thanks for
that by the way!) but they were not that obvious for me and I'm sure
other can benefit if they knew. So, how can I get write access to the
WIKI? or maybe I can give my notes to someone and that someone update
the wiki? I think they can help anybody trying to attempt the APK
compilation in the future.

Regards,
Taksan


questions about compilation and publishing of the APK

taksantong@...
 

Hello everyone, first: Thanks for all the people that make this project!

Ok now my comments: I compiled the espeak APK for a friend (he needs it and he is not a developer like me), and now I have these questions:

1.- Is there any official place to put and/or find compiled APKs? I will be doing more of these compiles and my friend is not the only one needing it, others want to try the latest also.

2.- The final step of the wiki is to "sign" the APK. Well, it does not work for me. Looks like something is wrong with my keys, something about MDA or SHA1 not correct because the error says something about the encryption algorithm being wrong. So, I had to use Android Studio at the end to at least get to a "debug" version of the APK. Has anybody used that last "sign" command successfully? exactly as described there? or the encryption algorithm changed but whe wiki needs updating?

3.- Speaking of the wiki... I had to install and do some extra steps to make the compilation work in my box (ubuntu). I would like to add those details and steps I did in the wiki, they are probably very obvious to whoever wrote the android section of the wiki (thanks for that by the way!) but they were not that obvious for me and I'm sure other can benefit if they knew. So, how can I get write access to the WIKI? or maybe I can give my notes to someone and that someone update the wiki? I think they can help anybody trying to attempt the APK compilation in the future.

Regards,
Taksan


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

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

1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
46f935d9de69: en: pronunciation fixes, including some Irish names/words

Modified: dictsource/en_list
Modified: dictsource/en_rules

Re: two issues to report

kendell clark
 

hi

I just wanted to add that it's possible that the emoji issue is limited to linux only. Or more specifically, linux users using espeak ng with orca through speech dispatcher. I'm also not sure if console screen readers such as speakup or fenrir will be affected, although testing most definitely welcome. I'm not sure of course, but I don't think nvda or the sapi five version of espeak ng supports emoji yet. If not, ignore this message. I just don't want people to start going wait a minute I can't reproduce the bug and so on. I did notice that once this issue occurrs, espeak ng mangles the word "emoji" until orca is restarted. At which point it works for a bit until you encounter whatever is making espeak ng mangle emojis. What it does is it tacks on the last mangled emoji onto the end of the word "emoji". So I got something taht sounded like emojiAleftEyeSpeechBubbleIs"

Thanks

Kendell Clark

On 07/14/2017 03:51 AM, kendell clark wrote:
hi all

A couple of issues to report this time. First, the word "hermit" as in, the lonely hermit is spoken like "you'll need a permit for that" instead of "I won't permit that." If that doesn't make sense, telling espeak to follow it's logic with espeak -v en-us -X hermit prints

Translate 'hermit'
1 h [h]

76 h) er (@ [3]
36 er [3:]
58 XC) er [3:]
1 e [E]

1 m [m]

1 i [I]

1 t [t]

h3m'It

The last issue is very very hard to pin down. The best advice I can give is to go through the emoji files for US english using the up, down, left and right arrows. You'll find all kinds of odd anomalies, where espeak seems to be putting bits of emojis onto the end of other emojis. I love the emoji support and I don't want it to go away. Also, this doesn't seem to affect espeak ng's normal reading of emoji, only when reading that file, although I'm not positive.

An example. Go to the very end of the emoji file and arrow up to the last emoji, past the source info lines. You should hear "eye in speech bubble."

What comes out is something like "a left eye in speech bubble."

That's just up and down arrowing. But if you use the left and right arrow, you get something like " "I left speech bubble is." Go to the right and you get "left speech bubble is".

This is odd. The emoji right above this one is the one about the postman and the flag, so some parts are being tacked on to the emoji I'm reading. If this is not an issue, but deliberate behavior I apologize, but it certainly seems like a bug.


Thanks for any help

Kendell Clark

two issues to report

kendell clark
 

hi all

A couple of issues to report this time. First, the word "hermit" as in, the lonely hermit is spoken like "you'll need a permit for that" instead of "I won't permit that." If that doesn't make sense, telling espeak to follow it's logic with espeak -v en-us -X hermit prints

Translate 'hermit'
1 h [h]

76 h) er (@ [3]
36 er [3:]
58 XC) er [3:]
1 e [E]

1 m [m]

1 i [I]

1 t [t]

h3m'It

The last issue is very very hard to pin down. The best advice I can give is to go through the emoji files for US english using the up, down, left and right arrows. You'll find all kinds of odd anomalies, where espeak seems to be putting bits of emojis onto the end of other emojis. I love the emoji support and I don't want it to go away. Also, this doesn't seem to affect espeak ng's normal reading of emoji, only when reading that file, although I'm not positive.

An example. Go to the very end of the emoji file and arrow up to the last emoji, past the source info lines. You should hear "eye in speech bubble."

What comes out is something like "a left eye in speech bubble."

That's just up and down arrowing. But if you use the left and right arrow, you get something like " "I left speech bubble is." Go to the right and you get "left speech bubble is".

This is odd. The emoji right above this one is the one about the postman and the flag, so some parts are being tacked on to the emoji I'm reading. If this is not an issue, but deliberate behavior I apologize, but it certainly seems like a bug.


Thanks for any help

Kendell Clark

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

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

13 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
da3ed3aa9bdd: Update the CHANGELOG to include the emoji-data properties.

Modified: CHANGELOG.md


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
6ff015f171e8: Use curl's -o to save the data files. This will prevent writing the file if the command fails.

Modified: Makefile.am


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
0b56f2e5bcd6: Use C-style comments to support using a C89 compiler.

Modified: CHANGELOG.md
Modified: src/case.c
Modified: src/categories.c
Modified: src/ctype.c
Modified: src/proplist.c
Modified: src/scripts.c
Modified: tests/printcdata.c
Modified: tests/printucddata.c
Modified: tools/case.py
Modified: tools/categories.py
Modified: tools/scripts.py


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
223d14bec8f3: Move the type declaration out of the for loops to support building with a C89 compiler.

Modified: tests/printcdata.c
Modified: tests/printucddata.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
bdc255835ecd: Provide a compatibility implementation of iswblank for C89 compilers.

Modified: .gitignore
Modified: configure.ac
Modified: tests/printcdata.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
4c1ff765f1dd: Unicode Character Data 10.0.0

Modified: CHANGELOG.md
Modified: src/categories.c
Modified: src/include/ucd/ucd.h
Modified: src/proplist.c
Modified: src/scripts.c
Modified: src/tostring.c
Modified: tools/scripts.py


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
023ebace9aa4: Add Regional_Indicator support from PropList.txt.

Modified: src/include/ucd/ucd.h
Modified: src/proplist.c
Modified: tools/printdata.py


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
18d3a0819a5e: Unicode Emoji 5.0

Modified: CHANGELOG.md
Modified: Makefile.am
Modified: src/proplist.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
1cb4115eabdd: Add Emoji_Component support from emoji-data.txt.

Modified: src/include/ucd/ucd.h
Modified: src/proplist.c
Modified: tools/printdata.py


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f26aca0aa1b9: ucd-tools 10.0.0

Modified: CHANGELOG.md


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
8566f2ee350c: Merge commit 'f26aca0aa1b9485634314d0d1710d2a0bb67776d'

Modified: src/ucd-tools/.gitignore
Modified: src/ucd-tools/CHANGELOG.md
Modified: src/ucd-tools/Makefile.am
Modified: src/ucd-tools/configure.ac
Modified: src/ucd-tools/src/case.c
Modified: src/ucd-tools/src/categories.c
Modified: src/ucd-tools/src/ctype.c
Modified: src/ucd-tools/src/include/ucd/ucd.h
Modified: src/ucd-tools/src/proplist.c
Modified: src/ucd-tools/src/scripts.c
Modified: src/ucd-tools/src/tostring.c
Modified: src/ucd-tools/tests/printcdata.c
Modified: src/ucd-tools/tests/printucddata.c
Modified: src/ucd-tools/tools/case.py
Modified: src/ucd-tools/tools/categories.py
Modified: src/ucd-tools/tools/printdata.py
Modified: src/ucd-tools/tools/scripts.py


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
3278ddaa721c: Update the UCD version to 10.0.0.

Modified: configure.ac


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
0b4d06dd9f1f: Merge commit '3278ddaa721c9a9d7de2415e64cba941e2e908f8'

Modified: src/ucd-tools/configure.ac

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

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

1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
d20422f1923c: en: various pronunciation fixes

Modified: dictsource/en_list
Modified: dictsource/en_rules

Re: espeak-ng for android and windows: new releases?

Simon Eigeldinger
 

Hi Reece,

OK i rechecked and it seems that something has fixed the issue.
now it works fine.
no clue what has broken that but before i got messages that it wasn't able to find voice data or other stuff.
not about dlls though because i had the right versions before.
weird.

Welcome to computers. *smile*

Greetings and thanks,
Simon


Am 06.07.2017 um 20:45 schrieb Reece H. Dunn:

On Thu, Jul 6, 2017 at 11:07 am, Simon Eigeldinger wrote:


Hi all,

Ayone knows when new releases are expected for espeak-ng for android and
windows?
I'm aiming for the end of the month for 1.49.2. The things still to do are:
* Update to Unicode 10.0.
* Support specifying the fallback language to use for Latin characters, allowing something like `fa,en-US` to replace the old `fa-en-us` voice.
* Add tests for all supported languages to the tests/languages.test file.
* Perform more testing on the English language rules to look for regressions.
* Test the Android port.


the windows port of 1.49.1 seem still broken.
the command line version isn't working on win 10 64 bit over here.
What problems are you experiencing? It works on the Windows 10 64-bit machine I use for testing.
Have you installed the Visual C++ Redistributable for Visual Studio 2015, mentioned in the README?
Kind regards,
Reece


Greetings,
Simon

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus ( 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 for android and windows: new releases?

Reece H. Dunn
 

On Thu, Jul 6, 2017 at 11:07 am, Simon Eigeldinger wrote:
Hi all,

Ayone knows when new releases are expected for espeak-ng for android and
windows?
I'm aiming for the end of the month for 1.49.2. The things still to do are:

  1. Update to Unicode 10.0.
  2. Support specifying the fallback language to use for Latin characters, allowing something like `fa,en-US` to replace the old `fa-en-us` voice.
  3. Add tests for all supported languages to the tests/languages.test file.
  4. Perform more testing on the English language rules to look for regressions.
  5. Test the Android port.

the windows port of 1.49.1 seem still broken.
the command line version isn't working on win 10 64 bit over here.
What problems are you experiencing? It works on the Windows 10 64-bit machine I use for testing.

Have you installed the Visual C++ Redistributable for Visual Studio 2015, mentioned in the README?

Kind regards,
Reece

Greetings,
Simon

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

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

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

1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
58a036376296: Android: Fix the location of ucd-tools (it is now in src/ucd-tools).

Modified: android/jni/Android.mk

Updates to Github #github

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

[espeak-ng:master] Label added to issue #276 'ucd/ucd.h' file not found by Erhannis.


[espeak-ng:master] New Issue Created by Erhannis:
#276 'ucd/ucd.h' file not found

In trying to build for android, I perform the following steps:

./autogen.sh
./configure --with-gradle=android/
make apk-release

and get the following error:

cd android && ndk-build
make[1]: Entering directory `/home/erhannis/projects/espeak-ng/android'
[mips] Compile        : ttsespeak <= tokenizer.c
jni/../../src/libespeak-ng/tokenizer.c:3010: fatal error: 'ucd/ucd.h' file not found
#include <ucd/ucd.h>
         ^
1 error generated.
make[1]: *** [obj/local/mips/objs/ttsespeak/__/__/src/libespeak-ng/tokenizer.o] Error 1
make[1]: Leaving directory `/home/erhannis/projects/espeak-ng/android'
Makefile:2600 recipe for target 'jni' failed
make: *** [jni] Error 2

Updates to Github #github

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

[espeak-ng:master] Issue #243 Failing to compile espeak-ng.js with emscripten under MacOS closed by BenTalagan.


[espeak-ng:master] New Issue Created by rhdunn:
#246 Fix espeak-ng handling of Malayalam chillu-virama and letter dot reph.

In readclause.c, espeak changes U+0D4D (MALAYALAM SIGN VIRAMA) when followed by a ZERO WIDTH JOINER (U+200D) into the codepoint U+0D4E. The comment says "use this unofficial code for chillu-virama", however U+0D4E has been allocated to MALAYALAM LETTER DOT REPH. As such, this behaviour is broken (as espeak/espeak-ng are treating LETTER DOT REPH as a chillu-virama).

Any fix for this needs to identify and update the rule and list files to use the representation of these that the fix changes to.

The preferred approach would be to use the normalisation logic specified in Table 1 ("Atomic Encoding of Chillus") of the Unicode 5.1.0 documentation[2]. For example, mapping 0D23 0D4D 200D to 0D7A, and keeping unknown sequences unmodified (i.e. preserving the 0D4D 200D representation). The rule and list files should use the Unicode 5.1.0 preferred representation of the chillu letters NN, N, RR, L, LL, and K (U+0D7A - U+0D7F).

For the new tokenizer logic, these should have test cases to cover the different characters to ensure that the sequences are mapped correctly.

Reference:

  1. https://en.wikipedia.org/wiki/Malayalam_script#Chillus
  2. http://www.unicode.org/versions/Unicode5.1.0/#Malayalam_Chillu_Characters


[espeak-ng:master] New Issue Created by rhdunn:
#246 Fix espeak-ng handling of Malayalam chillu-virama and letter dot reph.

In readclause.c, espeak changes U+0D4D (MALAYALAM SIGN VIRAMA) when followed by a ZERO WIDTH JOINER (U+200D) into the codepoint U+0D4E. The comment says "use this unofficial code for chillu-virama", however U+0D4E has been allocated to MALAYALAM LETTER DOT REPH. As such, this behaviour is broken (as espeak/espeak-ng are treating LETTER DOT REPH as a chillu-virama).

Any fix for this needs to identify and update the rule and list files to use the representation of these that the fix changes to.

The preferred approach would be to use the normalisation logic specified in Table 1 ("Atomic Encoding of Chillus") of the Unicode 5.1.0 documentation[2]. For example, mapping 0D23 0D4D 200D to 0D7A, and keeping unknown sequences unmodified (i.e. preserving the 0D4D 200D representation). The rule and list files should use the Unicode 5.1.0 preferred representation of the chillu letters NN, N, RR, L, LL, and K (U+0D7A - U+0D7F).

For the new tokenizer logic, these should have test cases to cover the different characters to ensure that the sequences are mapped correctly.

Reference:

  1. https://en.wikipedia.org/wiki/Malayalam_script#Chillus
  2. http://www.unicode.org/versions/Unicode5.1.0/#Malayalam_Chillu_Characters


[espeak-ng:master] Issue #234 Support Android 6.0.1 and later. closed by rhdunn.


[espeak-ng:master] Issue #259 Reading decimal numbers in Spanish. closed by Christianlm.


[espeak-ng:master] Label added to issue #259 Reading decimal numbers in Spanish. by Christianlm.


[espeak-ng:master] New Issue Created by rhdunn:
#205 Document the phonemes used by each phonemetable

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#205 Document the phonemes used by each phonemetable

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#205 Document the phonemes used by each phonemetable

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#205 Document the phonemes used by each phonemetable

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#206 Standardize the phoneme features specified in the phonemetables

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#206 Standardize the phoneme features specified in the phonemetables

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#206 Standardize the phoneme features specified in the phonemetables

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#206 Standardize the phoneme features specified in the phonemetables

  • [ ] ph_afrikaans
  • [ ] ph_akan
  • [ ] ph_albanian
  • [ ] ph_amhari
  • [ ] ph_arabic
  • [ ] ph_aragon
  • [ ] ph_armenian
  • [ ] ph_assamese
  • [ ] ph_azerbaijani
  • [ ] ph_base2
  • [ ] ph_basque
  • [ ] ph_bengali
  • [ ] ph_bulgarian
  • [ ] ph_burmese
  • [ ] ph_catalan
  • [ ] ph_consonants
  • [ ] ph_croatian
  • [ ] ph_czech
  • [ ] ph_danish
  • [ ] ph_dari
  • [ ] ph_divehi
  • [ ] ph_dutch
  • [ ] ph_english
  • [ ] ph_english_n
  • [ ] ph_english_rp
  • [ ] ph_english_sc
  • [ ] ph_english_us
  • [ ] ph_english_wi
  • [ ] ph_english_wm
  • [ ] ph_esperanto
  • [ ] ph_estonian
  • [ ] ph_farsi
  • [ ] ph_finnish
  • [ ] ph_french
  • [ ] ph_french_ca
  • [ ] ph_georgian
  • [ ] ph_german
  • [ ] ph_greek
  • [ ] ph_greek_ancient
  • [ ] ph_greenlandic
  • [ ] ph_guarani
  • [ ] ph_gujarati
  • [ ] ph_haitian
  • [ ] ph_hindi
  • [ ] ph_hindi_base
  • [ ] ph_hungarian
  • [ ] ph_icelandic
  • [ ] ph_indonesian
  • [ ] ph_interlingua
  • [ ] ph_irish
  • [ ] ph_italian
  • [ ] ph_japanese
  • [ ] ph_kannada
  • [ ] ph_kazakh
  • [ ] ph_kinyarwanda
  • [ ] ph_korean
  • [ ] ph_kurdish
  • [ ] ph_kyrgyz
  • [ ] ph_latin
  • [ ] ph_latvian
  • [ ] ph_lithuanian
  • [ ] ph_lojban
  • [ ] ph_macedonian
  • [ ] ph_malayalam
  • [ ] ph_maltese
  • [ ] ph_manipuri
  • [ ] ph_marathi
  • [ ] ph_nahuatl
  • [ ] ph_nepali
  • [ ] ph_northern-sotho
  • [ ] ph_norwegian
  • [ ] ph_oriya
  • [ ] ph_oromo
  • [ ] ph_polish
  • [ ] ph_portugal
  • [ ] ph_pt_brazil
  • [ ] ph_punjabi
  • [ ] ph_romanian
  • [ ] ph_russian
  • [ ] ph_serbian
  • [ ] ph_setswana
  • [ ] ph_s_gaelic
  • [ ] ph_sinhala
  • [ ] ph_slovak
  • [ ] ph_slovenian
  • [ ] ph_spanish
  • [ ] ph_spanish_la
  • [ ] ph_swahili
  • [ ] ph_swedish
  • [ ] ph_tamil
  • [ ] ph_tatar
  • [ ] ph_telugu
  • [ ] ph_tibetan
  • [ ] ph_turkish
  • [ ] ph_urdu
  • [ ] ph_vietnam
  • [ ] ph_vietnam_hue
  • [ ] ph_vietnam_sgn
  • [ ] ph_welsh
  • [ ] ph_wolof
  • [ ] ph_yoruba
  • [ ] ph_zh
  • [ ] ph_zh_yue
  • [ ] phonemes


[espeak-ng:master] New Issue Created by rhdunn:
#207 Redesign the phonindex binary format.

The phonindex binary file contains the compiled phoneme instructions (ipa, ChangePhoneme, etc.). These instructions are stored in a format like how the opcodes of a CPU are stored in computer programs. The phonemes in the phontab binary file have a program value that points to the offset of the start of the instructions in the phonindex file. This works like a function in a CPU -- the instructions are executed until a return instruction is executed.

This model is good, but the way it is implemented in eSpeak is clunky. Data is packed into the opcodes, with the intention of making the compiled data as compact as possible. This makes it difficult to extend to support new functionality.

This issue is about restructuring the phonindex format to make it more extensible and maintainable. The opcodes should just identify the instruction type. Additional data/control codes should go in data following the opcode. Thus, the code should be able to interpret the instructions using a top-level switch (opcode).


[espeak-ng:master] New Issue Created by rhdunn:
#207 Redesign the phonindex binary format.

The phonindex binary file contains the compiled phoneme instructions (ipa, ChangePhoneme, etc.). These instructions are stored in a format like how the opcodes of a CPU are stored in computer programs. The phonemes in the phontab binary file have a program value that points to the offset of the start of the instructions in the phonindex file. This works like a function in a CPU -- the instructions are executed until a return instruction is executed.

This model is good, but the way it is implemented in eSpeak is clunky. Data is packed into the opcodes, with the intention of making the compiled data as compact as possible. This makes it difficult to extend to support new functionality.

This issue is about restructuring the phonindex format to make it more extensible and maintainable. The opcodes should just identify the instruction type. Additional data/control codes should go in data following the opcode. Thus, the code should be able to interpret the instructions using a top-level switch (opcode).


[espeak-ng:master] New Issue Created by rhdunn:
#207 Redesign the phonindex binary format.

The phonindex binary file contains the compiled phoneme instructions (ipa, ChangePhoneme, etc.). These instructions are stored in a format like how the opcodes of a CPU are stored in computer programs. The phonemes in the phontab binary file have a program value that points to the offset of the start of the instructions in the phonindex file. This works like a function in a CPU -- the instructions are executed until a return instruction is executed.

This model is good, but the way it is implemented in eSpeak is clunky. Data is packed into the opcodes, with the intention of making the compiled data as compact as possible. This makes it difficult to extend to support new functionality.

This issue is about restructuring the phonindex format to make it more extensible and maintainable. The opcodes should just identify the instruction type. Additional data/control codes should go in data following the opcode. Thus, the code should be able to interpret the instructions using a top-level switch (opcode).


[espeak-ng:master] New Issue Created by rhdunn:
#207 Redesign the phonindex binary format.

The phonindex binary file contains the compiled phoneme instructions (ipa, ChangePhoneme, etc.). These instructions are stored in a format like how the opcodes of a CPU are stored in computer programs. The phonemes in the phontab binary file have a program value that points to the offset of the start of the instructions in the phonindex file. This works like a function in a CPU -- the instructions are executed until a return instruction is executed.

This model is good, but the way it is implemented in eSpeak is clunky. Data is packed into the opcodes, with the intention of making the compiled data as compact as possible. This makes it difficult to extend to support new functionality.

This issue is about restructuring the phonindex format to make it more extensible and maintainable. The opcodes should just identify the instruction type. Additional data/control codes should go in data following the opcode. Thus, the code should be able to interpret the instructions using a top-level switch (opcode).


[espeak-ng:master] New Issue Created by rhdunn:
#208 Support updating the phonemes independently of the dictionaries.

Adding a new phoneme to a phonemetable causes dictionary files to locate the wrong phoneme. As long as all phonemes for a given language are present in that language's phoneme table, it should not matter where they are in the binary phoneme file data.

NOTE: This is also needed to use the same language dictionary file on different voice phoneme data (e.g. a de1 MBROLA voice phoneme data file).


[espeak-ng:master] New Issue Created by rhdunn:
#208 Support updating the phonemes independently of the dictionaries.

Adding a new phoneme to a phonemetable causes dictionary files to locate the wrong phoneme. As long as all phonemes for a given language are present in that language's phoneme table, it should not matter where they are in the binary phoneme file data.

NOTE: This is also needed to use the same language dictionary file on different voice phoneme data (e.g. a de1 MBROLA voice phoneme data file).


[espeak-ng:master] New Issue Created by rhdunn:
#208 Support updating the phonemes independently of the dictionaries.

Adding a new phoneme to a phonemetable causes dictionary files to locate the wrong phoneme. As long as all phonemes for a given language are present in that language's phoneme table, it should not matter where they are in the binary phoneme file data.

NOTE: This is also needed to use the same language dictionary file on different voice phoneme data (e.g. a de1 MBROLA voice phoneme data file).


[espeak-ng:master] New Issue Created by rhdunn:
#208 Support updating the phonemes independently of the dictionaries.

Adding a new phoneme to a phonemetable causes dictionary files to locate the wrong phoneme. As long as all phonemes for a given language are present in that language's phoneme table, it should not matter where they are in the binary phoneme file data.

NOTE: This is also needed to use the same language dictionary file on different voice phoneme data (e.g. a de1 MBROLA voice phoneme data file).


[espeak-ng:master] New Issue Created by rhdunn:
#220 Use continuous integration (CI) on all supported platforms

Requirements

  • [ ] Run all supported platforms within a single CI file, with status identifiable on each (can work around this using separate branches).
  • [ ] Run CI on Linux.
  • [ ] Run CI on BSD.
  • [ ] Run CI on Mac.
  • [ ] Run CI on Android (build and test on Linux using the Android SDK and NDK).
  • [ ] Run CI on Windows.
  • [ ] Status for each platform should be identifiable and displayed in the platform support table.
  • [ ] Status for the different compiler configurations (gcc+version, clang+version, etc.).
  • [ ] Status for the different Android platforms the tests have run on.
  • [ ] Status for the different Windows platforms the tests have run on.
  • [ ] Allow build artifacts (APK for Android, MSI for Windows) to be placed somewhere accessible for testing.


[espeak-ng:master] New Issue Created by rhdunn:
#220 Use continuous integration (CI) on all supported platforms

Requirements

  • [ ] Run all supported platforms within a single CI file, with status identifiable on each (can work around this using separate branches).
  • [ ] Run CI on Linux.
  • [ ] Run CI on BSD.
  • [ ] Run CI on Mac.
  • [ ] Run CI on Android (build and test on Linux using the Android SDK and NDK).
  • [ ] Run CI on Windows.
  • [ ] Status for each platform should be identifiable and displayed in the platform support table.
  • [ ] Status for the different compiler configurations (gcc+version, clang+version, etc.).
  • [ ] Status for the different Android platforms the tests have run on.
  • [ ] Status for the different Windows platforms the tests have run on.
  • [ ] Allow build artifacts (APK for Android, MSI for Windows) to be placed somewhere accessible for testing.


[espeak-ng:master] New Issue Created by rhdunn:
#220 Use continuous integration (CI) on all supported platforms

Requirements

  • [ ] Run all supported platforms within a single CI file, with status identifiable on each (can work around this using separate branches).
  • [ ] Run CI on Linux.
  • [ ] Run CI on BSD.
  • [ ] Run CI on Mac.
  • [ ] Run CI on Android (build and test on Linux using the Android SDK and NDK).
  • [ ] Run CI on Windows.
  • [ ] Status for each platform should be identifiable and displayed in the platform support table.
  • [ ] Status for the different compiler configurations (gcc+version, clang+version, etc.).
  • [ ] Status for the different Android platforms the tests have run on.
  • [ ] Status for the different Windows platforms the tests have run on.
  • [ ] Allow build artifacts (APK for Android, MSI for Windows) to be placed somewhere accessible for testing.


[espeak-ng:master] New Issue Created by rhdunn:
#220 Use continuous integration (CI) on all supported platforms

Requirements

  • [ ] Run all supported platforms within a single CI file, with status identifiable on each (can work around this using separate branches).
  • [ ] Run CI on Linux.
  • [ ] Run CI on BSD.
  • [ ] Run CI on Mac.
  • [ ] Run CI on Android (build and test on Linux using the Android SDK and NDK).
  • [ ] Run CI on Windows.
  • [ ] Status for each platform should be identifiable and displayed in the platform support table.
  • [ ] Status for the different compiler configurations (gcc+version, clang+version, etc.).
  • [ ] Status for the different Android platforms the tests have run on.
  • [ ] Status for the different Windows platforms the tests have run on.
  • [ ] Allow build artifacts (APK for Android, MSI for Windows) to be placed somewhere accessible for testing.

espeak-ng for android and windows: new releases?

Simon Eigeldinger
 

Hi all,

Ayone knows when new releases are expected for espeak-ng for android and
windows?
the windows port of 1.49.1 seem still broken.
the command line version isn't working on win 10 64 bit over here.

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 rhdunn:
#286 Support named conditional rules in dictionary files

The aim of this feature is to: 1. make the conditional rules easier to read; 2. allow the conditional rules to be more generic; 3. support more than the 9 conditional rules allowed by espeak (?1-?9).

Use Case 1: Accent Specific Rules

en_list dictionary file:

vase  v'A:z
vase  v'eIz  ?en-US

en-US language file:

rule en-US

Use Case 2: Accent Splits and Mergers

en_rules dictionary file:

ir  3:  ?bird-nurse # e.g. bird

en-GB language file:

rule bird-nurse term-nurse # FIR-FUR-FERN merger

In this example, the NURSE vowel (FIR-FUR-FERN merger) is treated as the special case. Without that, it will default to the rules for i and r, resulting in the correct pronunciation in Scottish English, etc..

Use Case 3: Yod

There are 4 types of yod (/j/) behaviour:

diphthong -- preserve archaic /Iu:/ clusters like 'yew' found in Welsh English, etc.
elision -- elide the diphthong (e.g. /nu/ for 'new' in American English).
coalescence -- /sj/ => /S/, /zj/ => /Z/, /dj/ => /dZ/ and /tj/ => /tS/ found in many varieties of English
preserving -- RP tends to preserve the yod sound in non-archaic clusters

These can occur in different environments in different accents. It should be possible to specify these behaviours in the pronunciation rules, then specify which behaviours apply in the language files.


[espeak-ng:master] Label added to issue #286 Support named conditional rules in dictionary files by rhdunn.