You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 9, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 9, 2025. It is now read-only.
1.The content in rita_lts.js is the same as the file freetts-1.2.2_src/freetts-1.2.2/com/sun/speech/freetts/lexicon/cmudict04_lts.txt, except that all the ax are replaced with ah. No new lts file is found in the latest freetts download.
2.In the first post you mentioned, the author was trying to do the same thing as we do.
From my research, she was trying to use the lts rules for this project: Poemage, a Visualization Tool in Support of Close Reading. I downloaded the source code, but I was only able to find cmudict04_lts.txt.
So I guess she didn't generate the file in the end, but I still reached out to her in email and hopefully she could provide us with some useful information.
3.The rules from the paper “Letter-to-sound rules for automatic translation of english text to phonetics" could be used as a reference if we want to fix the LTS results with some extra rules.
One thing I think that worth to mention here is that an update to the latest cmu dictionary might not improve the quality of LTS result (if the standard is the percentage of the same pronunciation given from the dictionary)
The aim of LTS rules is not to generate perfect pronunciation, but acceptable ones. Therefore for many cases, they are acceptable but is different than what we have in the dictionary
Cause the algorithm evaluates the letter to sound rules based on a rule format: [letter before]letter[letter behind] the "e" in "betray" and "abet" are considered in the same way. Cases like this won't be improved by an update version. Adding extra phonetics rules based on “Letter-to-sound rules for automatic translation of english text to phonetics" should help to improve the results in similar cases
Sometimes the issue even doesn't lie in lts but in the original cmu dictionary.
For example:
When I check the most two common differences we got from last comparison,
"-ness" and "-ed". They already have different pronunciation in cmu dictionary.
vanness v ae0 n iy1 s
vastness v ae1 s t n ax s
vetted v eh1 t ih0 d
vested v eh1 s t ax d
Therefore, when they are evaluated with pro
9CDB
bability, there must be certain cases when the result is not equal to the dictionary. And they are also hard to solve with manual rules.
Two aims: 1) to get the outputs matching; 2) to remove unnecessary entries from lexicons (entries whose pronunciation data matches the LTS engine, and whose POS can be correctly guessed, primarily 'nn')
Updating lts rules to the latest cmu dict won't help with aim one, adding extra rules should be more helpful in this case (prefix, suffix...)
It makes sense to me to remove nns/vb*, because we still keep the corresponding nn/vb in the dictionary. But I'm not sure whether we want to remove too many entries from lexicon. This could limit the result we can get from randomWord()
Are there some generic rules we can try to improve the LTS ? Alternatively, we might want to update the pronunciation in the dictionary to what is generated by LTS, if it is also correct (but not the same).
Am I correct that we the current dictionary has vb* , but not nns ? I think it will require too much work on the analysis side (containsWord, for example) to remove the vb* as well...
Activity
cqx931 commentedon May 9, 2017
Other LTS options: MaryTTS, The Festival Speech Synthesis System, CMU Sphinx
cqx931 commentedon May 10, 2017
1.The content in rita_lts.js is the same as the file
freetts-1.2.2_src/freetts-1.2.2/com/sun/speech/freetts/lexicon/cmudict04_lts.txt, except that all theaxare replaced withah. No new lts file is found in the latest freetts download.Some clues of how the file is generated:
https://sourceforge.net/p/freetts/discussion/137669/thread/4621013d/
http://www.festvox.org/docs/manual-2.4.0/festival_13.html#Building-letter-to-sound-rules
Reason why freetts didn't update the lts file to the latest cmudict
https://sourceforge.net/p/freetts/discussion/137669/thread/4e7c5229/?limit=25#5eb4
2.In the first post you mentioned, the author was trying to do the same thing as we do.
From my research, she was trying to use the lts rules for this project: Poemage, a Visualization Tool in Support of Close Reading. I downloaded the source code, but I was only able to find cmudict04_lts.txt.
So I guess she didn't generate the file in the end, but I still reached out to her in email and hopefully she could provide us with some useful information.
3.The rules from the paper “Letter-to-sound rules for automatic translation of english text to phonetics" could be used as a reference if we want to fix the LTS results with some extra rules.
cqx931 commentedon May 16, 2017
One thing I think that worth to mention here is that an update to the latest cmu dictionary might not improve the quality of LTS result (if the standard is the percentage of the same pronunciation given from the dictionary)
[letter before]letter[letter behind]the "e" in "betray" and "abet" are considered in the same way. Cases like this won't be improved by an update version. Adding extra phonetics rules based on “Letter-to-sound rules for automatic translation of english text to phonetics" should help to improve the results in similar casesFor example:
When I check the most two common differences we got from last comparison,
"-ness" and "-ed". They already have different pronunciation in cmu dictionary.
Therefore, when they are evaluated with pro 9CDB bability, there must be certain cases when the result is not equal to the dictionary. And they are also hard to solve with manual rules.
dhowe commentedon May 16, 2017
I see -- so what do you recommend?
cqx931 commentedon May 25, 2017
According to your aims in #97
Updating lts rules to the latest cmu dict won't help with aim one, adding extra rules should be more helpful in this case (prefix, suffix...)
It makes sense to me to remove nns/vb*, because we still keep the corresponding nn/vb in the dictionary. But I'm not sure whether we want to remove too many entries from lexicon. This could limit the result we can get from randomWord()
dhowe commentedon May 25, 2017
Are there some generic rules we can try to improve the LTS ? Alternatively, we might want to update the pronunciation in the dictionary to what is generated by LTS, if it is also correct (but not the same).
Am I correct that we the current dictionary has vb* , but not nns ? I think it will require too much work on the analysis side (containsWord, for example) to remove the vb* as well...