Hi Simon, I would rather make use of something like https://wixtoolset.org/documentation/manual/v3/msbuild/task_reference/heatdirectory.html to generate the installation for files in a given directory

Great. Thanks for doing this. MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, rep

There is experimental support that is commented out of the installer which enables the English voice (search for SAPI Voices in the Product.wxs file). It has some issues (like the last part of the aud

The files need to be added by hand. This is partially to ensure the languages are listed correctly in the installer, and partially to ensure the installed files each have a consistent GUID across buil

That's correct. 'A@' is used for START words (words typically spelled with 'ar'), while 'A:' is used for PALM words. These are documented at https://github.com/espeak-ng/espeak-ng/blob/master/docs/lan

For reporting mispronunciations, either creating an issue/ticket on GitHub, or listing them here on this e-group is fine. If reporting the mispronunciations to GitHub, it would be better to group misp

That approach makes sense. When adding the entries, use "// [211E] other" for the comment. It is part of the letterlike symbols, so should be placed there. I'm looking at converting the existing symbo

Only if you want to change the base voice/accent. It will be like selecting Edward, or any of the other voice variants. And it would be no different to other TTS programs where you specify the voice a

#github

Thanks for reporting the issue and providing examples. I have reverted the change that caused this issue -- it makes sense to keep the current behaviour for those words. It was a fix for names and wor

The file compiles fine if you build the phoneme files as well -- I added a new phoneme to the English phoneme table. The continuous integration build at https://travis-ci.org/espeak-ng/espeak-ng would

This should now be fixed in the latest commit of espeak-ng. Kind regards, Reece

Some changes were made to try and improve the German voice. Those didn't work, so I have now reverted them back to what they were before these changes. Kind regards, Reece

I have pushed a fix for this so espeak-ng now pronounces newsletter correctly. Thanks for reporting the issue. The problem was a result of some of the code cleanup work I have been doing, not changes

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 happe

Hi Christo, You can get it at https://raw.githubusercontent.com/espeak-ng/espeak-ng/master/dictsource/af_emoji. The translations come from the CLDR (Unicode Common Locale Data Repository - http://cldr

Neural network based speech synthesis is trained around a given language, so it is harder to get it to properly articulate sounds from another language. ESpeak supports around 100 languages, some of w

#github

Not yet. Implementation work is being tracked at https://github.com/espeak-ng/espeak-ng/issues/7. I don't have an estimate of when this will be completed, as there are many other things to work on in

There are no explicit plans to add any language to espeak-ng. However, I will not reject patches to add support for any language. It would be helpful if the person adding the language is familiar with

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

The Sindhi language is currently using the Arabic script. If the scripts have a 1:1 mapping (like Hiragana and Katakana in Japanese), the mapping could be done in the dictionary files. If it is more c