Date   

Pull Request Updated #github

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

[espeak-ng/espeak-ng] Pull request updated by tset-tset-tset:

#810 Add some patterns to ja_rules

Hi, I've added a missing pattern to ja_rules. This fix allows for words like "ふぉーす" .


Updates to Github #github

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

[espeak-ng:master] New Issue Created by nesrad:
#811 Improved Interlingua voice

Hi, I've created the file ia_list to improve pronunciation for the ia voice. I'm not sure how to add it to your project, so I'll just leave it here. ia_list.zip

Since Interlingua shares its sounds with the romance languages, I was wondering what steps would be needed to use existing mbrola voices like Italian.


[espeak-ng:master] New Issue Created by nesrad:
#811 Improved Interlingua voice

Hi, I've created the file ia_list to improve pronunciation for the ia voice. I'm not sure how to add it to your project, so I'll just leave it here. ia_list_new.zip

Since Interlingua shares its sounds with the romance languages, I was wondering what steps would be needed to use existing mbrola voices like Italian.


[espeak-ng:master] New Issue Created by nesrad:
#811 Improved Interlingua voice

Hi, I've created the file ia_list to improve pronunciation for the ia voice. I'm not sure how to add it to your project, so I'll just leave it here. ia_list.zip

Since Interlingua shares its sounds with the romance languages, I was wondering what steps would be needed to use existing mbrola voices like Italian.


Pull Request Opened #github

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

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

#813 SSML cleanup

Move SSML related logic from ReadClause to ProcessSsmlTag and to a new function ParseSsmlReference().

Contributes to #369 and should make locating SSML bugs easier.


Updates to Github #github

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

[espeak-ng:master] New Issue Created by rhdunn:
#812 Add rule logic to better support Japanese vowel lengthening rules

In Japanese, a Hiragana whose pronunciation ends with the vowel a can be lengthened by adding あ (full a), ぁ (short a), or ー (lengthen indicator). The same applies with the other vowels. This results in the following set of rules for each base Hiragana:

.L22    ぁ ー // long a

.group あ
    あ       a   // a
    あ (あL22 a   // aā
    ああ      a:  // ā
    あぁ      a:  // ā
    あー      a:  // ā

It would be better to have the following rules:

.L22    あ ぁ ー   // long a

.group あ
    あ [あL22 a   // a
    あL22        a:  // ā

This requires two changes to the espeak-ng rule logic: 1. Add a [b (or a different syntax) to mean "don't match this rule if the 'b' part matches, but if it does match then only consume the 'a' part". An equivalent a] b syntax should be added for supporting matches before the main matching segment. -- maybe something like a^) b (^c? 2. Support matching substitution groups (in this case L22) in the main matching text, not just in the pre/post sections. NOTE: This may require a special syntax to differentiate it from other text, so maybe something like ${...} to use a substitution group (A, L12, etc.)?


[espeak-ng:master] New Comment on Pull Request #810 Add some patterns to ja_rules
By rhdunn:

I've raised issue #812 about making it possible to simplify the Japanese Hiragana/Kiragana pronunciation rules.


[espeak-ng:master] reported: Add some patterns to ja_rules #github

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

[espeak-ng:master] New Comment on Pull Request #810 Add some patterns to ja_rules
By rhdunn:

Using separate vowels would mean that ああ would be pronounced differently to あぁ and あー, as /aa/ would have a slight pause compared to /a:/.

A possible solution would be to define a group for each long vowel set (a, e, i, o, u), e.g.:

.L22    ぁ ー // long a

then have a new rule such as:

    あ   a       // a
    あ (あL22 a       // aā
    ああ  a:      // ā
    あぁ  a:      // ā
    あー  a:      // ā

where the rule is a new rule to fix the case you describe. This would need to be done for each of the doubling rules.

This means that ああぁ and ああー will be pronounced as /aa:/. These rules cannot currently be simplified due to limitations in the espeak/espeak-ng rule processing logic. I'll raise a separate issue for that.


Updates to Github #github

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

[espeak-ng:master] New Comment on Pull Request #810 Add some patterns to ja_rules
By tset-tset-tset:

@rhdunn

Thank you for reviewing my PR. Sorry for the lack of explanation, here's why I removed "かあ", "すう", etc:.

  1. Currently, the "あ" is grouped with the "あ", ”ああ”, "あぁ", "あー".
  2. However, when "かあ" is present, "かあぁ" or "かあー" is recognized as "かあ" + "ぁ" or "かあ" + "ー". Therefore, when we process some of the words now, "(en)" comes up.

    $ echo 'コンピュータアート' | espeak-ng -x -v ja
    k'o N\ C'i _:(en)dZ'ap@ni:z(ja)l'et@ 'u _:(en)dZ'ap@ni:z(ja)l'et@ t'a 'a _:(en)dZ'ap@ni:z(ja)l'et@ t'o
    
    $ echo 'スウェーデン' | espeak-ng -x -v ja
    s'u 'u _:(en)dZ'ap@ni:z(ja)l'et@ _:(en)dZ'ap@ni:z(ja)l'et@ t'e _:(en)dZ'ap@ni:z(ja)l'et@ N\
    
  3. When I considered the above case, I thought it would be more appropriate for the case where ”かあ” becomes "kaa" rather than "ka:".


[espeak-ng:master] New Issue Created by nesrad:
#811 Improved Interlingua voice

Hi, I've created the file ia_list to improve pronunciation for the ia voice. I'm not sure how to add it to your project, so I'll just leave it here. ia_list.zip

Since Interlingua shares its sounds with the romance languages, I was wondering what steps would be needed to use existing mbrola voices like Italian.


[espeak-ng:master] reported: Add some patterns to ja_rules #github

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

[espeak-ng:master] New Comment on Pull Request #810 Add some patterns to ja_rules
By rhdunn:

  1. Add some patterns to ja_rules -- This commit looks good.
  2. Add more ja_rules patterns -- This commit looks good.

Remove the pattern that causes the conversion to fail / Remove more unnecessary parts

Why are you removing the 'かあ' etc. patterns in these commits? These are supported "lengthen" combinations -- see e.g. https://en.wiktionary.org/wiki/%E3%81%8B%E3%81%82 (かあ). From https://en.wikipedia.org/wiki/Hiragana: > Hiragana usually spells long vowels with the addition of a second vowel kana; for example, おかあさん (o-ka-a-sa-n, "mother").

Thus, when a vowel Hiragana matches the vowel part of the previous Hiragana, the vowel is lengthened.

NOTE: The removed parts are not the small versions of the characters (ぁ) but are the full-sized versions (あ) so the two rules are different. This is causing the tests to fail.


Pull Request Updated #github

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

[espeak-ng/espeak-ng] Pull request updated by tset-tset-tset:

#810 Add some patterns to ja_rules

Hi, I've added a missing pattern to ja_rules. This fix allows for words like "ふぉーす" .


Pull Request Updated #github

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

[espeak-ng/espeak-ng] Pull request updated by tset-tset-tset:

#810 Add some patterns to ja_rules

Hi, I've added a missing pattern to ja_rules. This fix allows for words like "ふぉーす" .


Pull Request Opened #github

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

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

#810 Add some patterns to ja_rules

Hi, I've added a missing pattern to ja_rules. This fix allows for words like "ふぉーす" .


[espeak-ng:master] reported: MBROLA download page for Windows is not working #github

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


[espeak-ng:master] reported: F-Droid (Request for packaging) - For info #github

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

[espeak-ng:master] New Comment on Issue #644 F-Droid (Request for packaging) - For info
By ArenaL5:

Perfect. Only the metadata are missing now. (Summary, description...)

You can follow either manual I linked earlier (Fastlane or Triple-T). As far as I can tell, the easiest way to do is to follow the Fastlane manual and add these nested folders to the root of this repository:

fastlane/metadata/android/en-US

and, inside the en-US folder, fill in the files short_description.txt and full_description.txt. Extra files can be added whenever you want following the instructions at https://gitlab.com/snippets/1895688; at the very least, I would add the app icon at fastlane/metadata/android/en-US/images/icon.png.

full_description.txt can be mostly copied from your README.md

After you add the skeleton for any of these systems, I can create a pull request to this repo to add translations to Spanish (Spain).


Updates to Github #github

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

1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
85a9e5534076: Update version according to configure.ac, src/windows/config.h and android/jni/include/config.h files

Modified: android/AndroidManifest.xml


[espeak-ng:master] New Comment on Issue #644 F-Droid (Request for packaging) - For info
By valdisvi:

@ArenaL5, I fixed fa_list file with commit cee1870 and AndroidManifest.xml file with commit AndroidManifest.xml 85a9e55 to the current development version.


1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
3030884809aa: Fix issue #801: Cherokee language support is broken

Modified: src/libespeak-ng/tr_languages.c


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@...>:
cee18705a05b: Remove '\03' (End of text) characters at the beginning of the file

Modified: dictsource/fa_list


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@...>:
38291f5e5945: Support up to 350 voices/languages

Modified: src/libespeak-ng/voices.c


[espeak-ng:master] reported: F-Droid (Request for packaging) - For info #github

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

[espeak-ng:master] New Comment on Issue #644 F-Droid (Request for packaging) - For info
By ArenaL5:

Hello there. I'm trying to speed up the inclusion in F-Droid (there hasn't been much progress in that request).

I created a merge request with a build recipe, and a maintainer has already replied. They're asking now for a one-sentence summary and a description.

Both used to be provided in the merge request (as you can see here) but they're following now a different approach: they'd like to add them directly to this repo, following either Fastlane's or Triple-T's format. This way, it's easier to update the icon, to add translations, changelogs, screenshots...

I can help you with translating them to Spanish from Spain, if you'd like.

There are also a couple of details that aren't absolutely necessary, but would simplify the recipe: - ~Replacing gradle:3.2.1 with gradle:3.4.0 in android/build.gradle (F-Droid servers auto-detect the version of Gradle they use, and the build doesn't work with gradle:3.2.1).~ (Nevermind, I was checking an old commit.) - Removing the three extraneous characters at the beginning of dictsource/fa_list (it's no visible in the link, but that file starts with three U+0003 END OF TEXT characters, so the servers mistake it for a binary file. - Updating the version code and the version number at android/AndroidManifest.xml too (this would enable F-Droid to automatically update your app when you tag a new release version).


[espeak-ng:master] reported: F-Droid (Request for packaging) - For info #github

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

[espeak-ng:master] New Comment on Issue #644 F-Droid (Request for packaging) - For info
By ArenaL5:

Hello there. I'm trying to speed up the inclusion in F-Droid (there hasn't been much progress in that request).

I created a merge request with a build recipe, and a maintainer has already replied. They're asking now for a one-sentence summary and a description.

Both used to be provided in the merge request (as you can see here) but they're following now a different approach: they'd like to add them directly to this repo, following either Fastlane's or Triple-T's format. This way, it's easier to update the icon, to add translations, changelogs, screenshots...

I can help you with translating them to Spanish from Spain, if you'd like.

There are also a couple of details that aren't absolutely necessary, but would simplify the recipe: - Replacing gradle:3.2.1 with gradle:3.4.0 in android/build.gradle (F-Droid servers auto-detect the version of Gradle they use, and the build doesn't work with gradle:3.2.1. - Removing the three extraneous characters at the beginning of dictsource/fa_list (it's no visible in the link, but that file starts with three U+0003 END OF TEXT characters, so the servers mistake it for a binary file.


Updates to Github #github

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

2 New Commits:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
b06f524f3290: Issue #783: add new voices to the synthesizer

Added: espeak-ng-data/voices/!v/Alicia
Added: espeak-ng-data/voices/!v/Demonic
Added: espeak-ng-data/voices/!v/Marco
Added: espeak-ng-data/voices/!v/UniRobot


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
09200187de11: Support up to 350 voices/languages

Modified: src/libespeak-ng/voices.c


[espeak-ng:master] New Comment on Issue #783 Add new voices to the synthesizer.
By valdisvi:

Thanks for contribution! Your voices are added to the project with commit b06f524.


[espeak-ng:master] Issue #783 Add new voices to the synthesizer. closed by comunicationVoices.


[espeak-ng:master] reported: Some wrong pronunciations of German words #github

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

[espeak-ng:master] New Comment on Issue #809 Some wrong pronunciations of German words
By hozosch:

I'll certainly see about getting rid of the obvious pronunciation errors i spot, but I'm not sure if I can get that different i to work. Bare with me please, I'm not a professional phonologist. I acquired Espeak's phonetic spelling out of interest and I was always wanting to correct mispronounced words I come across very often.


[espeak-ng:master] reported: Some wrong pronunciations of German words #github

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

[espeak-ng:master] New Comment on Issue #809 Some wrong pronunciations of German words
By MilkKnight:

Hmmmm, those words ending in "i" are interesting. They have the wrong stress and pronunciation, but I think your main focus lies on getting rid of the ː symbol in the IPA output. The thing is, my feedback on ESpeak is from a listener's point of view, and not what the phoneme output is. Those "i" sounds are all correct for me, but I may fix the pronunciation of those words, because apart from the, in your view, unnecessary ː, there's also a wrong sounding pronunciation in general. Profi $1, and shouldn't the "ue" in Muesli be ü?

Thanks for the quick reply. Yes, you are right, it should be ü, sorry about that. We train our own TTS model based on the outputs of espeak-ng, and it's different on iː and i, the first one gives us a long tail sound.

BTW, sorry for be annoying, when do you think we can get a cool new commit? :)

Thanks!

321 - 340 of 3747