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
@rhdunn Thank you for reviewing my PR. Sorry for the lack of explanation, here's why I removed "かあ", "すう", etc:.
[espeak-ng:master] New Issue Created by nesrad:
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@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Issue Created by rhdunn:
In Japanese, a Hiragana whose pronunciation ends with the vowel
It would be better to have the following rules:
This requires two changes to the espeak-ng rule logic:
1. Add
[espeak-ng:master] New Comment on Pull Request #810 Add some patterns to ja_rules
I've raised issue #812 about making it possible to simplify the Japanese Hiragana/Kiragana pronunciation rules.
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Issue Created by nesrad:
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:
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:
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@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Issue Created by repodiac:
Hi, I've written a small script and tutorial to extract roughly 10k German loan words from the German wiktionary, use their IPA code and convert it into Kirshenbaum syntax for import as dictionary ( If you're interested (don't know about possible license issues with wiktionary data) you could take this as a PR or alternatively, link to my repo for the curious reader/user. https://github.com/repodiac/espeak-ng_german_loan_words
[espeak-ng:master] New Comment on Issue #814 PR: Approx. 10,000 German loan words from DE-Wiktionary could be added to espeak-ng dictionary
Well, this certainly sounds very exciting! I don't have the permission to merge this though.
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Comment on Issue #814 PR: Approx. 10,000 German loan words from DE-Wiktionary could be added to espeak-ng dictionary
Well, I am not a lawyer into IP... but yes, it seems if you stick to "share alike" with the usage (i.e. to my understanding, nobody is for instance, allowed to make money with this data under a proprietary license...) it should be ok - what's espeak-ng's precise license on data usage btw.?
Generally speaking: it should be possible. I parse for specific strings in German coming from the markup and surroundings. In other languages, as I assume, there is the same markup but in another language!? But I don't know if other languages in Wiktionary also specify provenance of words (i.e. lean words)... but if so, then it should be straight forward. The code is documented - but I can "guide" you if you want to use if for a specific language, where to replace the respective strings probably. Everything from then onward stays the same.
[espeak-ng:master] New Comment on Issue #814 PR: Approx. 10,000 German loan words from DE-Wiktionary could be added to espeak-ng dictionary
Well, I am not a lawyer into IP... but yes, it seems if you stick to "share alike" with the usage (i.e. to my understanding, nobody is for instance, allowed to make money with this data under a proprietary license...) it should be ok - what's espeak-ng's precise license on data usage btw.?
Generally speaking: it should be possible. I parse for specific strings in German coming from the markup and surroundings. In other languages, as I assume, there is the same markup but in another language!? But I don't know if other languages in Wiktionary also specify provenance of words (i.e. lean words)... but if so, then it should be straight forward. The code is documented - but I can "guide" you if you want to use it also for another specific language, where to replace the respective strings probably. Everything from then onward stays the same.
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Comment on Issue #814 PR: Approx. 10,000 German loan words from DE-Wiktionary could be added to espeak-ng dictionary
Solution seems interesting and may be useful for other languages, where pronunciation is not easy deducted from writing. But I'm wondering why it needs docker to run Python script.
[espeak-ng:master] New Comment on Issue #814 PR: Approx. 10,000 German loan words from DE-Wiktionary could be added to espeak-ng dictionary
Solution seems interesting and may be useful for other languages, where pronunciation is not easy deducted from writing. But I'm wondering, why it needs docker to run Python script.
[espeak-ng:master] New Comment on Issue #814 PR: Approx. 10,000 German loan words from DE-Wiktionary could be added to espeak-ng dictionary
Docker is used for a "turn-key" solution - no manual download or anything, just hit the button when you want the most recent file update, so to speak. It is all source code so if you are tech savy enough you can simply run -- or invoke the method even -- the script for yourself ;-) However, all this does not answer my initial request: Either you might include it into your build/deploy process (as the tutorial says... there are "Compile errors" sometimes) or you might link somewhere to the repo for anyone interested in enriching his German phoneme dictionary!?
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Comment on Issue #811 Improved Interlingua voice
Thanks for contribution! It is included into the project with commit 5deac40.
Some notes:
1. as word list is very long, it is put in file
I left only first entry in
To use MBROLA Italian voice for Interlingua, look MBROLA voices guide and mb-it1 and it1 files as examples. [espeak-ng:master] Issue #811 Improved Interlingua voice closed by nesrad.
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Comment on Pull Request #813 SSML cleanup
To check for regressions, I first cherry-picked only commit 959bf26 and run make check with everything else the same. I got error:
Does it means, that current implementation actually is broken and doesn't work as expected?
Why in
with all commits applied it works with spaces removed.
[espeak-ng:master] New Comment on Pull Request #813 SSML cleanup
To check for regressions, I first cherry-picked only commit 959bf26 and run make check with everything else the same. I got error:
Does it means, that current implementation actually is broken and doesn't work as expected?
Why in
with all commits applied it works with these spaces removed.
[espeak-ng:master] New Comment on Pull Request #813 SSML cleanup
To check for regressions, I first cherry-picked only commit 959bf26 and run
Does it means, that current implementation actually is broken and doesn't work as expected?
Why in
with all commits applied it works with these spaces removed.
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
[espeak-ng:master] New Comment on Pull Request #813 SSML cleanup
I think, it is old problem which will be fixed, please add commit to make xml formatted nicer, and I'll merge it. In future, it is better to start by adding test before refactoring. That will allow to ensure, that it either didn't come worse, or it actually fixes some problem which was not found before.
[espeak-ng:master] New Comment on Pull Request #813 SSML cleanup
I think, it is old problem which will be fixed. Please add commit to make xml formatted nicer, and I'll merge it. In future, it is better to start by adding test before refactoring. That will allow to ensure, that it either didn't come worse, or it actually fixes some problem which was not found before.
|
|
espeak-ng@groups.io Integration <espeak-ng@...>
7 New Commits:
[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
Modified: src/libespeak-ng/synthesize.h
[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
Modified: src/libespeak-ng/readclause.c
[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
Modified: src/libespeak-ng/readclause.c
[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
Added: tests/ssml/references.expected
[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
Modified: src/libespeak-ng/readclause.c
[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
Modified: tests/ssml/references.ssml2
[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
Added: tests/ssml/references.expected [espeak-ng/espeak-ng] Pull request closed by valdisvi: Move SSML related logic from ReadClause to ProcessSsmlTag and to a new function ParseSsmlReference(). Contributes to #369 and should make locating SSML bugs easier.
|
|