[espeak-ng:master] New Comment on Issue #935 Install it in google colab? RuntimeError: espeak not installed on your system
By krigeta:

when i try to use this to install it in python

!pip install espeak-ng

I got this error

ERROR: Could not find a version that satisfies the requirement espeak-ng (from versions: none)
ERROR: No matching distribution found for espeak-ng

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

#936 Add female forms of "Ingenieur" to German exception list and treat gender asterisk as punctuation

Changes: - add 'Ingenieurin', 'Ingenieurinnen' to German exception list - add "_" modifier to asterisk, so that it will be treated as punctuation.

Rationale: Terms "Ingenieur" is pronounced correctly, whereas "Ingenieurin/Ingenieurinnen" are not. Asterisk ("Gendersternchen") is a quasi-standard for writing gender-inclusive text in German.

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

The _dict files go to /usr/share/espeak-ng-data/ on a typical install.

That error message seems weird in this situation. Check if you can compile other languages, like English (en). You'll need the files in dictsource/en_rules in your $PWD.

All of the other dicts were available in /usr/lib/x86_64-linux-gnu/espeak-ng-data/

I've managed to get english to write a wav file that speaks. I copied the ja_dict to the dictsource folder that is being read but espeak-ng still doesn't know it exists.

When I try to compile the languages from the dockerfile I get Segmentation fault

#expose local file to dictsource which has the rules folder `dictsource`
/usr/src/app/aeneas/output/dictsource# espeak-ng --compile en
Segmentation fault

All of this is reproducible from the dockerfile, so it should be easy to reproduce.

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

The _dict files go to /usr/share/espeak-ng-data/ on a typical install.

That error message seems weird in this situation. Check if you can compile other languages, like English (en). You'll need the files in dictsource/en_rules in your $PWD.

I don't think the standard install from apt-get is working. There is no usr/share/espeak-ng-data when you install by sudo apt-get install espeak-ng

All of the other dicts were available in /usr/lib/x86_64-linux-gnu/espeak-ng-data/

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

The _dict files go to /usr/share/espeak-ng-data/ on a typical install.

That error message seems weird in this situation. Check if you can compile other languages, like English (en). You'll need the files in dictsource/en_rules in your $PWD.

All of the other dicts were available in /usr/lib/x86_64-linux-gnu/espeak-ng-data/

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

The _dict files go to /usr/share/espeak-ng-data/ on a typical install.

That error message seems weird in this situation. Check if you can compile other languages, like English (en). You'll need the files in dictsource/en_rules in your $PWD.

All of the other dicts were available in /usr/lib/x86_64-linux-gnu/espeak-ng-data/

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

@kanjieater

This is reproducible with this Dockerfile: gist.github.com/kanjieater/79d86540215facb1cc383bbc73e34c08

Standard way to install built package of espeak-ng is sudo apt-get install espeak-ng or yum install espeak-ng etc. If this or other non-standard way to set up espeak-ng doesn't work, please report it to provider of that package or installation manager. We maintain only building process from the source.

I'm not sure which part in particular would be non-standard. As a Dockerfile it's already running as root. The apt-get install command then has espeak-ng in it. This seems like it's an issue with the building process.

# Make sure to install sudo to match command
RUN set -x \
      && apt-get update \
      && apt-get install -y sudo 

RUN sudo apt update \
 && sudo apt-get install -y espeak-ng

Surely something like this would be supported? Japanese is not found when espeak is installed espeak-ng --voices

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

@kanjieater

This is reproducible with this Dockerfile: gist.github.com/kanjieater/79d86540215facb1cc383bbc73e34c08

Standard way to install built package of espeak-ng is sudo apt-get install espeak-ng or yum install espeak-ng etc. If this or other non-standard way to set up espeak-ng doesn't work, please report it to provider of that package or installation manager. We maintain only building process from the source.

I'm not sure which part in particular would be non-standard. As a Dockerfile it's already running as root (so do I really need to sudo?). The apt-get install command then has espeak-ng in it. This seems like it's an issue with the building process.

# Make sure to install sudo to match command
RUN set -x \
      && apt-get update \
      && apt-get install -y sudo 

RUN sudo apt update \
 && sudo apt-get install -y espeak-ng

Surely something like this would be supported? Japanese is not found when espeak is installed espeak-ng --voices

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By kanjieater:

The _dict files go to /usr/share/espeak-ng-data/ on a typical install.

That error message seems weird in this situation. Check if you can compile other languages, like English (en). You'll need the files in dictsource/en_rules in your $PWD.

I don't think the standard install from apt-get is working. There is no usr/share/espeak-ng-data when you install by sudo apt-get install espeak-ng

[espeak-ng:master] New Comment on Issue #935 Install it in google colab? RuntimeError: espeak not installed on your system
By valdisvi:

Standard way to install built package of espeak-ng is sudo apt-get install espeak-ng or yum install espeak-ng etc. If this or other non-standard way to set up espeak-ng doesn't work, please report it to provider of that package/installation manager. We maintain only building process from the source.

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By valdisvi:

@kanjieater

This is reproducible with this Dockerfile: https://gist.github.com/kanjieater/79d86540215facb1cc383bbc73e34c08

Standard way to install built package of espeak-ng is sudo apt-get install espeak-ng or yum install espeak-ng etc. If this or other non-standard way to set up espeak-ng doesn't work, please report it to provider of that package or installation manager. We maintain only building process from the source.

[espeak-ng:master] New Comment on Issue #935 Install it in google colab? RuntimeError: espeak not installed on your system
By valdisvi:

Standard way to install built package of espeak-ng is sudo apt-get install espeak-ng or yum install espeak-ng etc. If this or other non-standard way to set up espeak-ng doesn't work, please report it to provider of that package or installation manager. We maintain only building process from the source.

[espeak-ng:master] New Issue Created by krigeta:
#935 Install it in google colab? RuntimeError: espeak not installed on your system

Hello, i tried to install it by using

!pip install espeak

ERROR: Could not find a version that satisfies the requirement espeak (from versions: none)
ERROR: No matching distribution found for espeak

!pip install python-espeak but getting this errors

Building phoneme dictionary: ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0.0%
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
/Multilingual_Text_to_Speech/utils/text.py in _phonemize(text, language)
     90         seperators = Separator(word=' ', phone='')
---> 91         phonemes = phonemize(text, separator=seperators, backend='espeak', language=language)
     92     except RuntimeError:

9 frames
**RuntimeError: espeak not installed on your system**

During handling of the above exception, another exception occurred:

FileNotFoundError                         Traceback (most recent call last)
/usr/local/lib/python3.7/dist-packages/epitran/simple.py in _load_g2p_map(self, code, rev)
     90         except IndexError:
     91             raise DatafileError('Add an appropriately-named mapping to the data/maps directory.')
---> 92         with open(path, 'rb') as f:
     93             reader = csv.reader(f, encoding='utf-8')
     94             orth, phon = next(reader)

FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.7/dist-packages/epitran/data/map/chinese.csv'

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By rhdunn:

The extended dictionaries are still relevant. When enabled, they add a lot of entries generated from a dictionary (which I believe is from the Unicode unihan database, but I'm not 100% sure on that). This allows distributions that want to save space to ignore the listx files. It also keeps the generated lists separate from the custom exception lists. -- Ideally, the listx files should be autogenerated from the unihan list, but I haven't figured out how to do that yet, what version was used for the original list (to compare when using a script to generate the list), and what changes (if any) were made to that process.

Ideally, espeak compatibility where possible is important. Especially around the use of espeak. So keeping the old names in the lang files allows users/applications that have e.g. zh set as their TTS voice for orca/spech-dispatcher/etc. to still work when using espeak-ng. Likewise if/when they are using the espeak API. Therefore, the language zh 8, etc. should stay, but changing the dictionary/language file names should be OK as users don't directly interact with those.

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By jaacoppi:

I've refactored zhy to yue without problems. Two questions for @rhdunn before I push the changes: 1) Are the extended dictionaries and original espeak compatibility still relevant? Do we keep them or can we simplify and just use one _lsit file per language like for most languages? See commit f67221120 to refresh your memory.

2) the codebase has instances of "zh" (like the switch case in tr_languages.c and the language tags in espeak-ng-data/lang/sit/cmn and espeak-ng-data/lang/sit/zhy. There's "language zh-cmn", "language zh 8" and so on. Can I get rid of everything that mentions zh so that the code explicitly uses either Mandarin or Cantonese, not generic Chinese?

[espeak-ng:master] New Comment on Issue #922 Procedure not clear on how to remove/disable a language
By jbowler:

So far as what @jaacoppi suggests it's pretty trivial to try - just remove src/libespeak-ng/compile*.c from the source files for the library/DLL...

I just tested it, the library builds with no issues. I get (amd64 with -O2):

~/src/espeak-ng/master-build $ size !$/libespeak-ng.so.1.1.51
size src/.libs//libespeak-ng.so.1.1.51
   text    data     bss     dec     hex filename
 479817   31308  111464  622589   97ffd src/.libs/libespeak-ng.so.1.1.51

If I build the library with all the compile support:

~/src/espeak-ng/master-build $ size src/.libs//libespeak-ng.so.1.1.51
   text    data     bss     dec     hex filename
 533092   35708  155976  724776   b0f28 src/.libs//libespeak-ng.so.1.1.51

So that saves over 100k at run-time (text+data+bss). ROM usage depends primarily on the text - data tends to be highly compressible - and that only amounts to 53275 bytes, still that's 10%.

An espeak-ng static build with the "compile" options commented out should just do this automatically, and commenting out the five compile options is easy too...

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By jaacoppi:

So to confirm, I should compile the dictionaries using voice lang yue with zhy rules as well as using voice lang cmn with zhy rules to produce two dictionaries. Doing this seems to produce zhy_dict and zh_dict. If that is the case, it might be better for us just to have an explicit mapping rather than iterate over the files.

Yes, except for the typo (cmn uses zh rules, not zhy).

To say this in another way, at the moment: 1) "espeak-ng --compile=yue" uses zhyrules (and other zhy* files) to produce zhy_dict (Cantonese) 2) both "espeak-ng --compile=cmn" and "espea-ng --compile=zh" use zhrules (and other zh* files) to produce zh_dict (Mandarin)

Once I'm done with the restructuring: 1) --compile=zh will be deprecated (so make sure to start using --compile=cmn for Mandarin to avoid problems in the future) 2) zhy* files will be renamed yue* (you'll need to rename them in your build scripts) 3) zh* files will be renamed cmn* (you'll need to rename them in your build scripts)

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By feerrenrut:

So to confirm, I should compile the dictionaries using voice lang yue with zhy rules as well as using voice lang cmn with zhy rules to produce two dictionaries. Doing this seems to produce zhy_dict and zh_dict. If that is the case, it might be better for us just to have an explicit mapping rather than iterate over the files.

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By feerrenrut:

Ok, thanks @jaacoppi. We might go ahead with the work around for now. But it would be good to be able to remove it in the future. On the other hand, perhaps we should have an explicit listing of the voices to use with language rules to produce dictionaries.

[espeak-ng:master] New Comment on Issue #922 Procedure not clear on how to remove/disable a language
By Nafihahmd:

Thank you guys for your valuable replies. I was working on setting up the cross compiling toolchain for a couple days hence the delay in my reply. And to be frank I haven't quite understood what @jbowler had suggested. But I will work on it from today onward. I have started a separate fork where my development will be carried out as you have suggested.

[espeak-ng:master] New Comment on Issue #922 Procedure not clear on how to remove/disable a language
By Nafihahmd:

Thank you guys for your valuable replies. I was working on setting up the cross compiling toolchain for a couple days, hence the delay in my reply. And to be frank I haven't quite understood what @jbowler had suggested. But I will work on it from today onward. I have started a separate fork where my development will be carried out as you have suggested.

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By jaacoppi:

I'll try to rename yue_ and cmn_ files this weekend or next week. Looks like it's a bit more complicated than I thought because changes are needed in Android and Windows project files and in the language configuration files.

The dictionary files for Cantonese and Mandarin are different, you'll have to create both.

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By feerrenrut:

I misspoke in my last comment (now edited), we are deriving the language codes from the *_rules files not from *_dict files. But if the same offer applies to those files, that would also simplify this.

I have a potential work-around for this nvaccess/nvda#12370 however perhaps we are only creating one dictionary when we should be creating two?

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By jaacoppi:

Would it be easier for NVDA if there was yue_dict and cmn_dict instead of current zhy_dict and zh_dict?

The change for us should be easy since it's mostly about renaming files, not about changing code.

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By feerrenrut:

Thanks for the explanations. We are currently splitting the "zhy_rules" to get the language to switch to. I'll add an exception for that language.

[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By feerrenrut:

Thanks for the explanations. We are currently splitting the "zhy_dict" to get the language to switch to. I'll add an exception for that language.

[espeak-ng:master] New Comment on Issue #864 Can't find Japanese language code.
By jaacoppi:

The _dict files go to /usr/share/espeak-ng-data/ on a typical install.

That error message seems weird in this situation. Check if you can compile other languages, like English (en). You'll need the files in dictsource/en_rules in your $PWD.