Date   

Updates to Github #github

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

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

No luck still. Modifying the make file as you said resulted in the following error:

src/src_speak_ng-speak-ng.o: In function `main':
/home/melayil/Github/espeak-ng/src/espeak-ng.c:544: undefined reference to `espeak_ng_CompileIntonation'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:532: undefined reference to `espeak_ng_CompileMbrolaVoice'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:558: undefined reference to `espeak_ng_CompilePhonemeDataPath'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:560: undefined reference to `espeak_ng_CompilePhonemeData'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:632: undefined reference to `espeak_ng_CompileDictionary'
src/.libs/libespeak-ng.a(src_libespeak_ng_la-dictionary.o): In function `LookupDict2':
/home/melayil/Github/espeak-ng/src/libespeak-ng/dictionary.c:2784: undefined reference to `print_dictionary_flags'
/home/melayil/Github/espeak-ng/src/libespeak-ng/dictionary.c:2814: undefined reference to `print_dictionary_flags'
src/.libs/libespeak-ng.a(src_libespeak_ng_la-dictionary.o): In function `MatchRule':
/home/melayil/Github/espeak-ng/src/libespeak-ng/dictionary.c:2150: undefined reference to `DecodeRule'
src/.libs/libespeak-ng.a(src_libespeak_ng_la-espeak_api.o): In function `espeak_CompileDictionary':
/home/melayil/Github/espeak-ng/src/libespeak-ng/espeak_api.c:156: undefined reference to `espeak_ng_CompileDictionary'
collect2: error: ld returned 1 exit status
Makefile:1166: recipe for target 'src/speak-ng' failed
make[1]: *** [src/speak-ng] Error 1


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

Still no luck. Modifying the make file as you said resulted in the following error:

src/src_speak_ng-speak-ng.o: In function `main':
/home/melayil/Github/espeak-ng/src/espeak-ng.c:544: undefined reference to `espeak_ng_CompileIntonation'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:532: undefined reference to `espeak_ng_CompileMbrolaVoice'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:558: undefined reference to `espeak_ng_CompilePhonemeDataPath'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:560: undefined reference to `espeak_ng_CompilePhonemeData'
/home/melayil/Github/espeak-ng/src/espeak-ng.c:632: undefined reference to `espeak_ng_CompileDictionary'
src/.libs/libespeak-ng.a(src_libespeak_ng_la-dictionary.o): In function `LookupDict2':
/home/melayil/Github/espeak-ng/src/libespeak-ng/dictionary.c:2784: undefined reference to `print_dictionary_flags'
/home/melayil/Github/espeak-ng/src/libespeak-ng/dictionary.c:2814: undefined reference to `print_dictionary_flags'
src/.libs/libespeak-ng.a(src_libespeak_ng_la-dictionary.o): In function `MatchRule':
/home/melayil/Github/espeak-ng/src/libespeak-ng/dictionary.c:2150: undefined reference to `DecodeRule'
src/.libs/libespeak-ng.a(src_libespeak_ng_la-espeak_api.o): In function `espeak_CompileDictionary':
/home/melayil/Github/espeak-ng/src/libespeak-ng/espeak_api.c:156: undefined reference to `espeak_ng_CompileDictionary'
collect2: error: ld returned 1 exit status
Makefile:1166: recipe for target 'src/speak-ng' failed
make[1]: *** [src/speak-ng] Error 1


[espeak-ng:master] new issue: Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict #github

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

[espeak-ng:master] New Issue Created by BaijinBullet:
#938 Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict

Hello, I built successfully on Linux, but cannot be built on Windows using Visual Studio 2017.

Used: Visual Studio 2017 Community with C++ and others Windows 8.1 SDK WiX v.3.11.2.4516 pcaudiolib (today's clone)

I receive this:

3>------ Rebuild All started: Project: data, Configuration: Debug x64 ------
3>C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\data.vcxproj(80,5): error MSB3073: The command "C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\espeak-ng.exe --path=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\..\.. --compile-intonations" exited with code -1073741515.
3>Done building project "data.vcxproj" -- FAILED

Then:

4>------ Rebuild All started: Project: installer, Configuration: Debug x64 ------
4>		C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe -dDebug -d"DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\\" -dSolutionDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\ -dSolutionExt=.sln -dSolutionFileName=espeak-ng.sln -dSolutionName=espeak-ng -dSolutionPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\espeak-ng.sln -dConfiguration=Debug -dOutDir=bin\x64\Debug\ -dPlatform=x64 -dProjectDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\ -dProjectExt=.wixproj -dProjectFileName=installer.wixproj -dProjectName=installer -dProjectPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\installer.wixproj -dTargetDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\bin\x64\Debug\ -dTargetExt=.msi -dTargetFileName=espeak-ng.msi -dTargetName=espeak-ng -dTargetPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\bin\x64\Debug\espeak-ng.msi -despeak-ng.Configuration=Debug -d"espeak-ng.FullConfiguration=Debug|x64" -despeak-ng.Platform=x64 -despeak-ng.ProjectDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\ -despeak-ng.ProjectExt=.vcxproj -despeak-ng.ProjectFileName=espeak-ng.vcxproj -despeak-ng.ProjectName=espeak-ng -despeak-ng.ProjectPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\espeak-ng.vcxproj -despeak-ng.TargetDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\ -despeak-ng.TargetExt=.exe -despeak-ng.TargetFileName=espeak-ng.exe -despeak-ng.TargetName=espeak-ng -despeak-ng.TargetPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\espeak-ng.exe -dlibespeak-ng.Configuration=Debug -d"libespeak-ng.FullConfiguration=Debug|x64" -dlibespeak-ng.Platform=x64 -dlibespeak-ng.ProjectDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\ -dlibespeak-ng.ProjectExt=.vcxproj -dlibespeak-ng.ProjectFileName=libespeak-ng.vcxproj -dlibespeak-ng.ProjectName=libespeak-ng -dlibespeak-ng.ProjectPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\libespeak-ng.vcxproj -dlibespeak-ng.TargetDir=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\ -dlibespeak-ng.TargetExt=.dll -dlibespeak-ng.TargetFileName=libespeak-ng.dll -dlibespeak-ng.TargetName=libespeak-ng -dlibespeak-ng.TargetPath=C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\libespeak-ng.dll -out obj\x64\Debug\ -pedantic -arch x64 Product.wxs
4>		C:\Program Files (x86)\WiX Toolset v3.11\bin\Light.exe -out C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\bin\x64\Debug\espeak-ng.msi -pdbout C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\bin\x64\Debug\espeak-ng.wixpdb -cultures:null -pedantic -contentsfile obj\x64\Debug\installer.wixproj.BindContentsFileListnull.txt -outputsfile obj\x64\Debug\installer.wixproj.BindOutputsFileListnull.txt -builtoutputsfile obj\x64\Debug\installer.wixproj.BindBuiltOutputsFileListnull.txt -wixprojectfile C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\installer.wixproj -ext WixUIExtension obj\x64\Debug\Product.wixobj
4>C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\Product.wxs(346,0): error LGHT0103: The system cannot find the file 'C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\..\..\..\espeak-ng-data\phontab'.
4>C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\Product.wxs(349,0): error LGHT0103: The system cannot find the file 'C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\installer\..\..\..\espeak-ng-data\phonindex'.

I made some changes to libespeak so that it is build; before this, it did not work as well. If relevant, can provide.

Urgently need to build on Windows, thank you!


[espeak-ng:master] reported: Procedure not clear on how to remove/disable a language #github

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

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

You don't remove the files, rather you modify Makefile.am not to include them in the build; i.e. delete the three lines:

        src/libespeak-ng/compiledata.c \
        src/libespeak-ng/compiledict.c \
        src/libespeak-ng/compilembrola.c \

from the definition of src_libespeak_ng_laSOURCES and whichever of the phsource/ph* lines and espeak-ng-data/*_dict lines that you don't need to build. Although, since espeak_ng won't be able to do the compile operations you probably don't even want to bother with the latter; just comment out the 'all-local' target at the top of Makefile.am

For tr_translate.c you have to comment out the languages. BTW this is for an experiment or a one-time unsupportable hack for a particular system. Actually doing it in the project would require some way of choosing the languages at 'configure' time, some support for the same in the Visual Studio solution and extra configure options such as --enable-ssml plus a somewhat tricky change to allow espeak-ng to be built twice, once with compile support once without, or maybe --enable-compile.


Updates to Github #github

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

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

Your method was very quick buddy. Removed SSML functionality. I just had to add 2 dummy functions. I will write the new ssml.c below.



#include "config.h"

#include <ctype.h>
#include <errno.h>
#include <locale.h>
#include <math.h>
#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <wchar.h>
#include <wctype.h>


#include <espeak-ng/espeak_ng.h>
#include <espeak-ng/speak_lib.h>
#include <espeak-ng/encoding.h>
#include <ucd/ucd.h>

#include "ssml.h"
#include "dictionary.h"           // for strncpy0
#include "mnemonics.h"               // for LookupMnemName, MNEM_TAB, 
#include "readclause.h"           // for PARAM_STACK, param_stack, AddNameData
#include "soundicon.h"               // for LoadSoundFile2
#include "synthesize.h"           // for SPEED_FACTORS, speed
#include "translate.h"            // for CTRL_EMBEDDED, IsDigit09, utf8_out
#include "voice.h"                // for SelectVoice, SelectVoiceByName

static MNEM_TAB ssmltags[] = {
	{ "speak",     SSML_SPEAK },
	{ "voice",     SSML_VOICE },
	{ "prosody",   SSML_PROSODY },
	{ "say-as",    SSML_SAYAS },
	{ "mark",      SSML_MARK },
	{ "s",         SSML_SENTENCE },
	{ "p",         SSML_PARAGRAPH },
	{ "phoneme",   SSML_PHONEME },
	{ "sub",       SSML_SUB },
	{ "tts:style", SSML_STYLE },
	{ "audio",     SSML_AUDIO },
	{ "emphasis",  SSML_EMPHASIS },
	{ "break",     SSML_BREAK },
	{ "metadata",  SSML_IGNORE_TEXT },

	{ "br",     HTML_BREAK },
	{ "li",     HTML_BREAK },
	{ "dd",     HTML_BREAK },
	{ "img",    HTML_BREAK },
	{ "td",     HTML_BREAK },
	{ "h1",     SSML_PARAGRAPH },
	{ "h2",     SSML_PARAGRAPH },
	{ "h3",     SSML_PARAGRAPH },
	{ "h4",     SSML_PARAGRAPH },
	{ "hr",     SSML_PARAGRAPH },
	{ "script", SSML_IGNORE_TEXT },
	{ "style",  SSML_IGNORE_TEXT },
	{ "font",   HTML_NOSPACE },
	{ "b",      HTML_NOSPACE },
	{ "i",      HTML_NOSPACE },
	{ "strong", HTML_NOSPACE },
	{ "em",     HTML_NOSPACE },
	{ "code",   HTML_NOSPACE },

	{ NULL, 0 }
};

/********* Dummy Functions *********/

int ProcessSsmlTag(wchar_t *xml_buf, char *outbuf, int *outix, int n_outbuf, const char *xmlbase, bool *audio_text, char *current_voice_id, espeak_VOICE *base_voice, char *base_voice_variant_name, bool *ignore_text, bool *clear_skipping_text, int *sayas_mode, int *sayas_start, SSML_STACK *ssml_stack, int *n_ssml_stack, int *n_param_stack, int *speech_parameters)
{
	return 0;
}

int ParseSsmlReference(char *ref, int *c1, int *c2) {

	return -1; //Failure to Parse

}

And now to the real business. With SSML |file | size (bytes) | |libespeak-ng.a |2,584,008 | |libespeak-ng.so |1,557,248 |

Without SSML |file | size (bytes) | |libespeak-ng.a |2,516,848 | |libespeak-ng.so |1,514,088 |


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

Your method was very quick buddy. Removed SSML functionality. I just had to add 2 dummy functions. I will write the new ssml.c below.



#include "config.h"

#include <ctype.h>
#include <errno.h>
#include <locale.h>
#include <math.h>
#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <wchar.h>
#include <wctype.h>


#include <espeak-ng/espeak_ng.h>
#include <espeak-ng/speak_lib.h>
#include <espeak-ng/encoding.h>
#include <ucd/ucd.h>

#include "ssml.h"
#include "dictionary.h"           // for strncpy0
#include "mnemonics.h"               // for LookupMnemName, MNEM_TAB, 
#include "readclause.h"           // for PARAM_STACK, param_stack, AddNameData
#include "soundicon.h"               // for LoadSoundFile2
#include "synthesize.h"           // for SPEED_FACTORS, speed
#include "translate.h"            // for CTRL_EMBEDDED, IsDigit09, utf8_out
#include "voice.h"                // for SelectVoice, SelectVoiceByName

static MNEM_TAB ssmltags[] = {
	{ "speak",     SSML_SPEAK },
	{ "voice",     SSML_VOICE },
	{ "prosody",   SSML_PROSODY },
	{ "say-as",    SSML_SAYAS },
	{ "mark",      SSML_MARK },
	{ "s",         SSML_SENTENCE },
	{ "p",         SSML_PARAGRAPH },
	{ "phoneme",   SSML_PHONEME },
	{ "sub",       SSML_SUB },
	{ "tts:style", SSML_STYLE },
	{ "audio",     SSML_AUDIO },
	{ "emphasis",  SSML_EMPHASIS },
	{ "break",     SSML_BREAK },
	{ "metadata",  SSML_IGNORE_TEXT },

	{ "br",     HTML_BREAK },
	{ "li",     HTML_BREAK },
	{ "dd",     HTML_BREAK },
	{ "img",    HTML_BREAK },
	{ "td",     HTML_BREAK },
	{ "h1",     SSML_PARAGRAPH },
	{ "h2",     SSML_PARAGRAPH },
	{ "h3",     SSML_PARAGRAPH },
	{ "h4",     SSML_PARAGRAPH },
	{ "hr",     SSML_PARAGRAPH },
	{ "script", SSML_IGNORE_TEXT },
	{ "style",  SSML_IGNORE_TEXT },
	{ "font",   HTML_NOSPACE },
	{ "b",      HTML_NOSPACE },
	{ "i",      HTML_NOSPACE },
	{ "strong", HTML_NOSPACE },
	{ "em",     HTML_NOSPACE },
	{ "code",   HTML_NOSPACE },

	{ NULL, 0 }
};

/********* Dummy Functions *********/

int ProcessSsmlTag(wchar_t *xml_buf, char *outbuf, int *outix, int n_outbuf, const char *xmlbase, bool *audio_text, char *current_voice_id, espeak_VOICE *base_voice, char *base_voice_variant_name, bool *ignore_text, bool *clear_skipping_text, int *sayas_mode, int *sayas_start, SSML_STACK *ssml_stack, int *n_ssml_stack, int *n_param_stack, int *speech_parameters)
{
	return 0;
}

int ParseSsmlReference(char *ref, int *c1, int *c2) {

	return -1; //Failure to Parse

}

And now to the real business. With SSML |file | size (bytes) | --------------------- | ---------------- |libespeak-ng.a |2,584,008 | |libespeak-ng.so |1,557,248 |

Without SSML |file | size (bytes) | --------------------- | ---------------- |libespeak-ng.a |2,516,848 | |libespeak-ng.so |1,514,088 |


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

#937 Updates italian source dictionaries

Improvements to rules for irregular/pronominal verbs and exceptions.


[espeak-ng:master] reported: Procedure not clear on how to remove/disable a language #github

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

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

@jaacoppi, Thanks. I will use the first method you said. Previously I was going by the second method and it felt very cumbersome.


[espeak-ng:master] reported: Install it in google colab? RuntimeError: espeak not installed on your system #github

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

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

Try

pip install py-espeak-ng

Espeak and Espeak-ng are different by the way


[espeak-ng:master] reported: Procedure not clear on how to remove/disable a language #github

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

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

The build system (Gnu Make) expects those files to exist. You'll get an error if you remove them.

One way to do it is to delete everything, just leave an empty file. Then recompile and wait for the compiler to give error messages about missing functions. Then create dummy functions for those parts.

Another way is to look through the code and figure out where each function is called and why. Then delete everything you don't need.


[espeak-ng:master] reported: Procedure not clear on how to remove/disable a language #github

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

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

Hi @jbowler , as you said I removed all compile*.c tried recompiling. But it is giving me errors. Let me elaborate the steps I followed.

  1. I moved compile*.c files out of the main folder

    mv src/libespeak-ng/compile*.c ../
    
  2. I recompiled the code using make -B

  3. Now in the middle of compiling I am getting the following error.

    CC       src/ucd-tools/src/src_libespeak_ng_la-tostring.lo
    make[1]: *** No rule to make target 'src/libespeak-ng/compiledata.c', needed by 'src/libespeak-ng/src_libespeak_ng_la-compiledata.lo'.  Stop.
    make[1]: Leaving directory '/home/melayil/Github/espeak-ng'
    Makefile:749: recipe for target 'all' failed
    make: *** [all] Error 2
    

N.B: I get similar error if I remove ssml.c file also (make[1]: *** No rule to make target 'src/libespeak-ng/ssml.c,...')

N.B 2: I think @jaacoppi was asking to removing only parts of .c file in his previous post. If that is the case, how should I remove functions inside the .c files without effecting other code that will be calling the former function. Should I leave a dummy function with no code inside?


[espeak-ng:master] reported: Install it in google colab? RuntimeError: espeak not installed on your system #github

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

[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


Pull Request Opened #github

espeak-ng@groups.io Integration <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] reported: Can't find Japanese language code. #github

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

[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/ image

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.


Updates to Github #github

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

[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/ image


Updates to Github #github

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

[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 image


[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 image


[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


Updates to Github #github

espeak-ng@groups.io Integration <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: Install it in google colab? RuntimeError: espeak not installed on your system #github

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

[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] reported: Unable to compile zhy dictionay on Windows #github

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

[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] reported: Unable to compile zhy dictionay on Windows #github

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

[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] reported: Procedure not clear on how to remove/disable a language #github

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

[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] reported: Unable to compile zhy dictionay on Windows #github

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

[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] reported: Unable to compile zhy dictionay on Windows #github

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

[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.

801 - 820 of 4890