Date   

[espeak-ng:master] reported: Wrong/Confusing Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong/Confusing Identifiers
By gelodefaultbrain:

Ohhh okay okay got it! Thank you! :D Yes I am using espeak as the backend :) as you can see on the screenshot :D So Spanish Latin American is es-la ?

Thank you so much!

I think it would be nice if the developers could put the correct identifiers for every backend if some of them are different base on the backend cause tbh it's kinda confusing and I am using this package for future projects... Thank you so much :D

would love to just check the docs for the identifiers :D Thank you! Please if possible update the identifiers for each backend.. Thank you! again!


[espeak-ng:master] reported: NVDA Announcement Issue #github

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

[espeak-ng:master] New Comment on Issue #818 NVDA Announcement Issue
By sukiletxe:

Cannot confirm, both in NVDA 2020.2 and 2020.3 beta 1. Can you give more details (NVDA version, synth, voice, complete examples where it fails?) I've tested with strings "31/12/2020" and "No", and the results are correct in English Great Britain. I'm using the Male3 variant.


[espeak-ng:master] new issue: NVDA Announcement Issue #github

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

[espeak-ng:master] New Issue Created by RituAdhikari:
#818 NVDA Announcement Issue

Announcing on date format (dd/ mm/yyyy) mm when language selected as Great Britain but when language is united state it is announcing correctly Announcing No as number when language selected as United states but when language is great Britain it is announcing "no" correctly


[espeak-ng:master] reported: Wrong/Confusing Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong/Confusing Identifiers
By rhdunn:

Hmm. Based on which identifiers work and which don't, it looks like you are using espeak for the voices/languages, not espeak-ng. Those names (es-la, etc.) are the espeak names; it does not support several of the names such as es-419.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Please take a look at this , this is what I am talking about

image

I tried to use the es-419 identifier for spanish latin america and it doesn't work both on the CMD and in python

image image

Now the thing I am concern is on the docs the identifier of this is es-419

image

Now I am just wondering why is that? could the identifier just be different? and what is it? Thank you!


[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

As you can see I tried also es-la and es and the results are different, I am wondering that es-la could be the spanish latin american while es is Spain


[espeak-ng:master] New Issue Created by gelodefaultbrain:
#816 Wrong/Confusing Identifiers

Hello! I would like to share my experience with this, this library is great and it helped me a lot :D

Just want to add up that the identifier for French is not "fr" I think ti should be indicated there "fr-fr" and I am thinking that this could apply to other languages as well. In this British right there where I boxed it, it is not identified in python , I am thinking that it's the wrong identifier again. Can you guys double check it :D Thank you!

image

image


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Hello, I am running this with python but the code "es-419" does not work :(


[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Hello, I am running this with python but the code "es-419" does not work :(

May I ask what could be the correct code? the language="es-419" does not work


[espeak-ng:master] reported: Wrong Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

I tried running that in python where language = "es-la" and it worked... hmmmm... may I ask why is that? Thank you!


[espeak-ng:master] reported: Wrong Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By valdisvi:

There is no voice es-la in eSpeak NG defined therefore it is simplified to just es.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Hello I also tried this getting the IPA from Spanish Latin America

I tried this code data_ipa = phonemize(data,language="es-419",backend="espeak")

and it doesn't work it says unrecognized language code, do you might have happened to have a list of the correct codes or Identifiers? :D Thank you!

image


[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Look :D when I tried "es-la" it worked! May I ask is this the same as "es-419", does "es-la" mean latin america? Thank you!


[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Look :D when I tried "es-la" it worked! May I ask is this the same as "es-419", does "es-la" mean latin america? Thank you!

image


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

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

1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
ec7ebfb3c676: lv: add more unstressed words

Modified: dictsource/lv_list


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By valdisvi:

Input words should be lowercase. If you want to mark that word should start or be entire in uppercase, you mark it with additional flags like $capital or $allcaps.


[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By repodiac:

Okay, thanks again. I close the issue then


[espeak-ng:master] Issue #817 Broken import of multi-word terms from extra dictionary!? closed by repodiac.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By repodiac:

Ok, I just checked out your suggestion: It works only, if I use lower-case so that the term is (common sense) !?! I first tried (Common Sense) which resulted in k'Omo:n z'Enz@ -- in literally pronounced German but not the correct English pronounciation!

Did I miss something or is only lowercase allowed with imports? Does this make sense overall, I mean you loose information on being substantive for a word for instance in German.


[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By repodiac:

Ok, I just checked out your suggestion: It works only, if I use lower-case so that the term is (common sense) !?! I first tried (Common Sense) which resulted in k'Omo:n z'Enz@ -- in literally pronounced German but not the correct English pronounciation!

Did I miss something or is only lowercase allowed with imports? Does this make sense overall, I mean you loose information on being substantive for a word for instance in German.

PS: I also checked the link you referred to above, it does not state that import dictionaries have to be lowercase...


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By valdisvi:

Are you sure you have imported entry according to the rules? It should look like:

(common sense) ,kOm@n'||sEns

because otherwise second word sense is assumed to be pronunciation and everything else after that is ignored.


[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By valdisvi:

Probably yo have not imported entry according to the rules. It should look like:

(common sense) ,kOm@n'||sEns

because otherwise second word sense is assumed to be pronunciation and everything else after that is ignored.


[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By valdisvi:

Probably you have not imported entry according to the rules. It should look like:

(common sense) ,kOm@n'||sEns

because otherwise second word sense is assumed to be pronunciation and everything else after that is ignored.


[espeak-ng:master] New Comment on Issue #817 Broken import of multi-word terms from extra dictionary!?
By repodiac:

Oh great - thank you for the quick response! I'll look into it...


Updates to Github #github

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

[espeak-ng:master] New Issue Created by repodiac:
#817 Broken import of multi-word terms from extra dictionary!?

Hi,

when working on a German loan word dictionary (https://github.com/espeak-ng/espeak-ng/issues/814), to be imported as de_extra into espeak-ng, I figured that often/always(?) terms with more than one word are either rejected or -- worse - imported but somewhat crippled.

An example: Importing the term common sense into the German de_extra dictionary results in S'ense z'Enz@

$ espeak-ng -v German "Common Sense" -x
S'ense z'Enz@

Is this as expected -- then: why? and how can I provide for a proper import? -- or is this likely a bug? Thanks for any help!


[espeak-ng:master] New Issue Created by repodiac:
#817 Broken import of multi-word terms from extra dictionary!?

Hi,

when working on a German loan word dictionary (https://github.com/espeak-ng/espeak-ng/issues/814), to be imported as de_extra into espeak-ng, I figured that often/always(?) terms with more than one word are either rejected or -- worse - imported but somewhat crippled.

An example: Importing the term common sense as entry ,kOm@n'sEns into the German de_extra dictionary results in S'ense z'Enz@

$ espeak-ng -v German "Common Sense" -x
S'ense z'Enz@

Is this as expected -- then: why? and how can I provide for a proper import? -- or is this likely a bug? Thanks for any help!


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Hello! Thank you so much for your reply I am using this to get the IPA of words from different languages :D Here is the code where I use the phonemizer library :D

image

The last time I tried for the language french and on the documentation it was said to be "fr" then I discovered on your other docs using the espeak ng -v [LANG] I think that's on the terminal right? that it is "fr-fr" for french so I got it! :D

Now I am trying right now for the West Germanic English Received Pronunciations and I tried the en-gb-x-rp and as you can see on the previous images that it doesn't recognize it, and I think I am just inputting the wrong specifier for it so may I ask what would be the right specifier for it? Thank you! this library is really awesome and helps a lot :D


[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

data_ipa = phonemize(data,language="en-gb-x-rp",backend="espeak")

This does not work and it doesn't recognize the language parameter value which is en-gb-x-rp I am just thinking that I am putting the wrong specifier just like what happened with French cause what I did is put "fr" and I soon discovered that it should be "fr-fr" so maybe yeah I am just putting the wrong specifier :D would you happen to have a list of it? :D Thank you!


[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

By the way I am not using any of the commands using the terminal, tho I've tried it :D as of now I am using this with python and it's really helpful


[espeak-ng:master] reported: Wrong Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By rhdunn:

The identifiers marked are the BCP 47 language tags for the supported languages. Because fr has a default country code of FR, you can omit that from the tag as is done here. Also, the dialects use the private tags (-x-[tag]) from https://raw.githubusercontent.com/espeak-ng/bcp47-data/master/bcp47-extensions. Also note that BCP 47 tags are case insensitive.

The language file for en-gb-x-rp is lang/gmw/en-GB-x-rp, so maybe that issue is with a case sensitive check/match? However, note that the file contains the following:

language en-gb-x-rp
language en-gb  4
language en 5

so using the (espeak_/espeakng)SetVoiceByName/SetVoiceByProperties APIs should be matching the language correctly.

The French (France) voice is located in lang/roa/fr, so that is correct. Note that that file defines the following languages:

language fr-fr
language fr

so should accept either fr or fr-fr.

What program/python binding are you using? Do you know how that python binding is checking for the language? Do you get the same issue using espeak-ng -v [LANG]?


[espeak-ng:master] reported: Wrong Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

"en-gb" works but that "en-gb-x-rp" does not work


[espeak-ng:master] reported: Wrong Identifiers #github

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

[espeak-ng:master] New Comment on Issue #816 Wrong Identifiers
By gelodefaultbrain:

Also on your .md it says "fr" and it should be "fr-fr" cause in python and on the documentation you have you guys indicated it "fr-fr" that's where I learned that it is not "fr". It's kinda confusing and it might help others too. Thank you!

image


[espeak-ng:master] new issue: Wrong Identifiers #github

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

[espeak-ng:master] New Issue Created by gelodefaultbrain:
#816 Wrong Identifiers

Hello! I would like to share my experience with this, this library is great and it helped me a lot :D

Just want to add up that the identifier for French is not "fr" I think ti should be indicated there "fr-fr" and I am thinking that this could apply to other languages as well. In this British right there where I boxed it, it is not identified in python , I am thinking that it's the wrong identifier again. Can you guys double check it :D Thank you!

image

image


[espeak-ng:master] reported: Reimplement the SAPI bindings. #github

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

[espeak-ng:master] New Comment on Issue #7 Reimplement the SAPI bindings.
By amirsol81:

Folks, may I humbly know why no SAPI 5 installer exists or hasn't been released for this project? It will open lots of opportunities on Windows in combination with apps like JAWS. The old eSpeak SAPI 5 is quite crash-prone on Windows.

281 - 300 of 3751