2020-07 - Roots

If you have any words you would like added to the root dictionary, please comment below. If the word has US and UK spellings that are different but should be pronounced the same in American English, please include both. All entries if possible should be as a general American English accent would say it. Post your words here, and if you can applicable pronunciations. These can either be in eloquence direct phoneme format, or as some other descriptor. If you can't convey these properly but you know of another American English synthesizer that pronounces the word as intended, you can reference that and we will extrapolate the phonemes from that. Although if the word is common enough but just hasn't been caught yet, we should most likely know how to handle it, thus intended pronunciations are optional.
Note that the root dictionary is encoded in an ANSI codepage, for English Windows 1252, so along with Eloquence's rules about the contents of entries keep in mind that only characters in this set can be part of entries. Thus some fancy accented letters that are not in 1252 but are in Unicode may have difficulty being added, depending on how the encoding handler replaces them.

I propose the word solenoid (/ˈsoʊlənɔɪd/ according to Wikipedia, this may be British IPA. IDK, can't read it. I think it's something along the lines of soalenoid?

Here are some entries, some have a comment before them starting with # to explain why they're there.
beautician	`[.0byu.1tIS.0xn]
Alex, host of Jeopardy!
trebek	`[.0trX.1bEk]
The service you use to find info about domain registrations
whois	`[.1hu.0Iz]
Nick
giannak	`[.1JAn.0Xk]
Classic interactive fiction/text adventure company from the 80's. Responsible for Zork and many others
infocom	`[.1Info.0kam]
One of Mars's moons
phobos	[.1fo.0bos] sndup	[.0Es.0En.0di.1Hp]
ncaa	[.0En.0si.0dHbxl.1e] naacp	[.0En.0dHbxl.0e.0si.1pi]
A trigger fish from Hawaii
humuhumunukunukuapua'a	[.0humx.0humx.0nukx.0nukx.0ap.0u.0a.1a] kitchensinc	[.1kIC.0xnz.1IGk]
Russian special forces
spetsnaz	`[.0spEtz.1nyaz]
A kind of pasta
penné	[.0pxn.1e] textfiles	[.1tEkst.0fYlz]
textfile	`[.1tEkst.0fYl]
Abbreviation for University of Louisville
uofl	`[.0yu.0xv.1El]
A games company from the 80's
broderbund	[.1brod.0R.0bHnd] thermocouple	[.1TR.0mx.0kH.0pxl]
Jonathan
mosen	[.1mo.0zxn] mushroomfm	[.1mHS.0rum.0Ef.1Em]
The CPU used in the Apple II and others
6502	[.0sIks.0ti.0fYv.0o.1tu] werewolf	[.1wer.0wxlf]
fjord	[.1fyord] adolf	[.1ed.0clf]
adolph	[.1ed.0clf] freedomscientific	[.0fri.0dxm.0sY.0xn.1tIf.0Xk]
Software maintenance agreement
sma	[.0Es.0Em.1e] callsign	[.1kcl.0sYn]
openvpn	[.1o.0pxn.0vi.0pi.1En] aes	[.0e.0i.1Es]
sos	[.0Es.0o.1Es] cpu	[.0si.0pi.1yu]
gpu	[.0Ji.0pi.1yu] edelweiss	[.1ed.0xl.0vYs]
A temperature/humidity sensor
sensorpush	`[.1sEn.0sR.0pUS]
A city in North Carolina
durham	[.1dU.0rxm] runaround	[.1rHn.0x.0rWnd]
A medicine
flonase	`[.1flo.0nez]
A certain man with two heads from the Hitchhiker's Guide to the Galaxy
zaphod	[.1ze.0fad] beeblebrox	[.1bi.0bxl.0braks]
Another guy from the same.
slartibartfast	`[.0slar.0ti.1bart.0fAst]
Regrettably your planet is one of those scheduled for demolition by these guys
vogon	[.1vo.0gan] thermostats	[.1TR.0mx.0stAts]
walmart	[.1wcl.0mart] kroger	[.1kro.0gR]
meijer	`[.1mY.0R]
The guy who invented the Step by Step phone switch
strowger	`[.1stro.0JR]
Speech synthesis software for the Apple II
textalker	`[.1tEks.0tckR]
An operating system for the Apple II
prodos	[.1pro.0das] probraille	[.1pro.0brel]
One of at least sixteen possible spellings of this word.
hanukkah	[.1han.0xkx] siriusxm	[.1sir.0i.0xs.0Eks.1Em]
xmradio	[.1Eks.1Em.1red.0i.0o] tunein	[.1tun.0In]
amazonsmile	[.1Amx.0zan.1smYl] fergie	[.1fR.0gi]
Weird Al
yankovic	`[.1yAGk.0x.0vIk]
A breed of dog
dachshund	`[.1daks.0xn]
A city in Kentucky
louisville	[.1lu.0x.0vxl] budweiser	[.1bHd.0wY.0zR]
A language spoken in Africa
swahili	`[.0swa.1hi.0li]
From StarTrek TOS
uhura	[.0u.1hu.0rx] rachmaninoff	[.0rak.1ma.0nx.0naf]
tchaikovsky	`[.0CY.1kaf.0ski]
An electric toothbrush
sonicare	`[.1sanX.0ker]
This streaming service would be broadcasting the Barbershop Harmony Society's international convention this week, except it's been canceled due to Coronavirus
flovoice	[.1flo.0vOs] adeline	[.1Ad.0x.0lYn]
A text editor
edsharp	[.1Ed.0Sarp] boucher	[.0bu.1Se]
deauthorize	[.0di.1cT.0R.0Yz] euterpe	[.0yu.1tR.0pi]
nomorobo	[.0no.0mo.1ro.0bo] nuc	[.1nUk]
oldschool	[.1old.0skul] rsgames	[.1ar.1Es.1gemz]
Bruce
toews	[.1tevz] videogame	[.1vI.0dio.0gem]
imap	[.1Y.0mAp] mbox	[.1Em.0baks]
sqlite	[.0Es.0kyu.1lYt] mysql	[.0mY.0Es.0kyu.1El]
rsa	[.0ar.0Es.1e] directv	[.0dR.1Ek.1ti.1vi]
nlsbard	[.0En.0El.0Es.1bard] wifi	[1wY0fY]
sidharth	[1sId0harT] anneke	[1an0X0kx]
mbraille	`[1Em0brel]
A rather famous virus
coronavirus	[.0kR.1o.0nx.0vY.0r.0xs] brigham	[.1brI.0gxm]
ourself	[.0Wr.1sElf] webinar	[.1wEb.0X.0nar]
hourglass	[.1WR.0glAs] mailto	[.1mel.0tu]
icann	[.1Y.0kAn] godaddy	[.1go.0dAdi]
deregister	`[.0di.1rE.0JX.0stR]
A famous poet
yeats	[.1yets] lexicon	[.1lE.0ksX.0kan]
palmolive	[.0pam.1al.0Xv] csun	[.1si.0sHn]
tbrnlive	[.0ti.0bi.0ar.0En.1lYv] winamp	[.1wIn.0Amp]
xmplay	[.0Eks.0Em.1ple] ibmtts	[.0Y.0bi.0Em.1ti.1ti.1Es]
flickr	[.1flI.0kR] tumblr	[.1tHm.0blR]
komplete	[.0kxm.1plit] kontrol	[.0kxn.1trol]
qatar	[.0kx.1tar] istanbul	[.0Ist.0an.1bUl]
retinitis	[.0rE.0?N.1Y.0tXs] pigmentosa	[.0pIg.0mXn.1to.0sx]
dakotan	[.0dX.1ko.0txn] macular	[.1mAk.0yx.0lR]
stroganoff	[.1strog.0xn.0cf] squawk	[.1skwak]
John
clower	[.1klW.0R] ibm	[.0Y.0bi.1Em]
aph	[.0e.0pi.1eC] plugin	[.1plH.0gIn]
xbox	[.1Eks.0baks] covid	[.1ko.0vXd]
gramophone	[.1grA.0mx.0fon] animorphs	[.1An.0X.0morfs]
sewer	[.1su.0R] sewage	[.1su.0XJ]
alienation	[.0e.0li.0xn.1eS.0xn] wellbeing	[.0wEl.1bi.0IG]
miniscule	[.1mI.0nx.0skyul] emojis	[.0I.1mo.0Jiz]
murderbot	[.1mxr.0dxr.0bat] postmate	[.1post.0met]
delphi	[.1dEl.0fY] munawar	[.1mu.0nx.0war]
whatnot	[.1wHt.0nat] refill	[.1ri.0fIl]

Done (849ae32). The default appears to be British pronunciation, weirdly.

I propose the word solenoid (/ˈsoʊlənɔɪd/ according to Wikipedia, this may be British IPA. IDK, can't read it. I think it's something along the lines of soalenoid?

Done (849ae32). The default appears to be British pronunciation, weirdly.

@jaybird110127 Wow, this is brilliant, thanks for your the submissions! Have to check standard pronunciations for 1 or 2 things, and will leave those abbreviations for their own dictionary for now, but most of these should be in there. Keep an eye out and open an issue if you notice something amiss.
Thanks for taking the time!

I say we should exclude 6502, uofl, that should be an NVDA dictionary thing since there's so many and they may overlap, yankovic and louisville already work, possibly others. And NAACP is already cane care of by eloquence, you're supposed to capitalize those acronyms. NCAA also works.

Oh, Louisville is different there. I'm not sure how widespread that is. Do we know other states with Louisvilles to compare it to? Also I'm not sure what to do with cpu and gpu, as they're supposed to be CPU and GPU, in uppercase, and actually getting multi-word SPR's in the roots is a royal pain in the ass, see idk and others.

yankovic and louisville already work

Louisville is being researched right now, but he wasn't wrong about Yankovic (/ˈjæŋkəvɪk/ - YANK-a-vik).

Adds most of the non-abbreviation entries from @jaybird110127, (187ebf2) alterations below. Thanks!

Fobos is traditionally pronounced /ˈfoʊbɒs/ (FO.boss).
There are a few ways to pronounce humuhumunukunukuapua'a, will look into this.
Have picked the most general American pronunciation of Dachshund I could find, not quite like yours.
Have decided not to add Louisville just yet, the pronunciation seems region-specific. Am open to correction.
Have not added rsgames - As said above, multi-word SPRs can be difficult to make natural in the roots dictionary, and this one just sounded very stilted and clumsy.
Did not ad sewer yet, because unfortunately this is a homonym and I'm not sure which meaning should take precedence.
Added refill for trial. It's a noun and a verb, and while it is the noun which is mispronounced, eloquence itself seems to have trouble distinguishing the forms, and I'm not sure if this'll help or make it worse.
Fixed a few confusions between the two qualities of schwa (X and x).
Turned the /ɒ/ in your pronunciation of "squawk" into a /ɔː/

Proposing hallucinogen.
In my part of the US, which isn't the region it covers but this might be the same pronunciation, it would be something like `[h0xl1usXnx2Jxn]. Maybe some switching on those schwas, though, like should the last one right before the n be the ih shaped or uh shaped one.

Dictionaries.zip
Guys, to say that you have turned my 15-year-old hobby into a serious undertaking would be a huge understatement!
I've been correcting Eloquence mispronunciations for the last 15 years, and actually have a hefty Root.dic file here. Older versions of my file used to ship with Nuance TALKS&ZOOMS and the Kurzweil 1000 which are both very much considered to be defunct (sadly of course). At any event, as an NVDA user, I have been correcting Eloquence mispronunciations for my own pleasure and managed to share the Root file with many users.
I'm attaching my Root and Main files to this message. My question is how we can merge my gigantic root file with the one being maintained here. Of course, I just took a look at the Root file provided as part of this project, and noticed that both files have many common words. One final point is that since I can't get IBM TTS 20.07-x0_personal to detect ABBR.dic, I'm using Main.dic for abbreviations.
Cheers.

@amirsol81 Hi there. It'd be difficult to exaggerate just how helpful you've been to the project, so I won't try. I will, however, say a huge thanks,  of course! Fifteen years of customisations is nothing to turn one's nose up at, and it'd be absurd not to include your hard work here!
I'll need to write a program that can compare these files and print the differences, but be sure you'll see your work incorporated into (and credited in) a near-future release, hopefully the next on 08-01.
Blown away by this, thanks again, and hoping you're well!

I'll look into not loading ABBR.dic, though do keep in mind that you have to have abbreviations turned on in the synth. Also the latest IBMTTS compiles are only loading root.dic, main.dic and abbr.dic as legacy filenames, they will begin prefering enuroot.dic, enumain.dic and enuabbr.dic, which is for compatibility with another driver, though unfortunately they haven't yet had this same support added for other languages. If you could please upload your dictionaries again but with the abbreviations in abbr.dic that would be great.

Is this the same dictionary set referenced by Spivey and his add-on that automatically updates them?

@amirsol81 Hi there. It'd be difficult to exaggerate just how helpful you've been to the project, so I won't try. I will, however, say a huge thanks, of course! Fifteen years of customisations is nothing to turn one's nose up at, and it'd be absurd not to include your hard work here!
I'll need to write a program that can compare these files and print the differences, but be sure you'll see your work incorporated into (and credited in) a near-future release, hopefully the next on 08-01.
Blown away by this, thanks again, and hoping you're well!

Thanks for your kind words! I'm glad my love of language and my attention to one of the best TTS engines ever produced finally paid off! I'd be ecstatic to contribute to the project, and am positive we'll have awesome discussions regarding word pronunciations in the near future.
All the best,
Amir

I'll look into not loading ABBR.dic, though do keep in mind that you have to have abbreviations turned on in the synth. Also the latest IBMTTS compiles are only loading root.dic, main.dic and abbr.dic as legacy filenames, they will begin prefering enuroot.dic, enumain.dic and enuabbr.dic, which is for compatibility with another driver, though unfortunately they haven't yet had this same support added for other languages. If you could please upload your dictionaries again but with the abbreviations in abbr.dic that would be great.

Hmm. This is a bit baffling. No matter what I do, I can't get IBMTTS to detect and use ENUabbr.dic or Abbr.dic. The same variations work well for Root and Main, but Abbr never gets detected. I do have that Abbreviation check box checked in NVDA's Voices dialog.
Of course, your decision regarding the use of ENU as part of the file names is quite welcome as it means I won't need to alter the file names. Kurzweil 1000's SAPI 4 Eloquence works with the ENU prefix, and I use that version of Eloquence and its provided Eloq.exe to correct mispronunciations.
As for Abbr.dic/ENUAbbr.dic, anything I can try?
Thanks.

Is this the same dictionary set referenced by Spivey and his add-on that automatically updates them?

I don't know. But I have updated mine over the past couple of weeks quite significantly. Even new words like "allowlist" are included.

I'll look into not loading ABBR.dic, though do keep in mind that you have to have abbreviations turned on in the synth. Also the latest IBMTTS compiles are only loading root.dic, main.dic and abbr.dic as legacy filenames, they will begin prefering enuroot.dic, enumain.dic and enuabbr.dic, which is for compatibility with another driver, though unfortunately they haven't yet had this same support added for other languages. If you could please upload your dictionaries again but with the abbreviations in abbr.dic that would be great.

I'm still trying to get ABBR/ENUABBR to work, but apparently to no avail. Even Eloquence SAPI 4 which ships with the K1000 can't detect its entries. So I haven't been able to transfer abbreviations from ENUMain.dic to ENUAbbr.dic. But attached is a ZIP file contining my latest dictionaries -- I added some entries to both files over the last couple of hours.
Eloq ENU Dictionaries.zip

Yes, that addon does reference this dictionary. However, I am kind of concerned about this root dictionary and merging it. One of the main issues I encountered with it in quite a lot of instances where either your dialect was inserted, or pronunciations just made things sound weird or were were a bit wrong, for example Adidas. It seems that the original German pronunciation is [.1a.0Fi.2das], not [.1H.0FX.2dHs].

Yes, that addon does reference this dictionary. However, I am kind of concerned about this root dictionary and merging it. One of the main issues I encountered with it in quite a lot of instances where either your dialect was inserted, or pronunciations just made things sound weird or were were a bit wrong, for example Adidas. It seems that the original German pronunciation is [.1a.0Fi.2das], not [.1H.0FX.2dHs].

Well, as far as English is concerned, I can't have a so-called dialect bias because I'm an Iranian with an M.A. degree in TESL. But I love American English and consider myself an avid NPR/Public Radio listener. I also check top US dictionaries such as AHD5, Merriam-Webster, Dictionary.com and Lexico (an offshoot of Oxford) when I want to make pronunciation modifications.
As for Adidas, since I wanted to alter the popular American pronunciation which is quite different from the original and since it's not defined in any major American English dictionary, I consulted a number of online sources including the following to select the one you see in the file: https://www.insider.com/how-to-pronounce-adidas-2016-12#:~:text=It's pronounced "AH-dee-,emphasis on the first syllable.&text=The brand is derived from,Ah-DEE-dus."
That said, I just provided my files here in case they can help the project move forward more promptly. There will be nothing wrong with not including them or modifying/removing the words people might deem erroneous.

Yes, that addon does reference this dictionary. However, I am kind of concerned about this root dictionary and merging it. One of the main issues I encountered with it in quite a lot of instances where either your dialect was inserted, or pronunciations just made things sound weird or were were a bit wrong, for example Adidas. It seems that the original German pronunciation is [.1a.0Fi.2das], not [.1H.0FX.2dHs].

That's why the project is on GitHub! :-) so that we can collaborate on and discuss these things as they come up, and obviously we will need a merge process for such a large set of entries. But I don't see this as being a barrier.
Also, regarding words like Adidas, we are transcribing pronunciations for a general American dialect of English. While I agree with you and think you're right about the native (and more correct) German pronunciation) of the word, I personally believe our goal should be to remain faithful to the dialect, not each word's origins. We can discuss the things we find and do some research.

Yes, that addon does reference this dictionary. However, I am kind of concerned about this root dictionary and merging it. One of the main issues I encountered with it in quite a lot of instances where either your dialect was inserted, or pronunciations just made things sound weird or were were a bit wrong, for example Adidas. It seems that the original German pronunciation is [.1a.0Fi.2das], not [.1H.0FX.2dHs].

That's why the project is on GitHub! :-) so that we can collaborate on and discuss these things as they come up, and obviously we will need a merge process for such a large set of entries. But I don't see this as being a barrier.
Also, regarding words like Adidas, we are transcribing pronunciations for a general American dialect of English. While I agree with you and think you're right about the native (and more correct) German pronunciation) of the word, I personally believe our goal should be to remain faithful to the dialect, not each word's origins. We can discuss the things we find and do some research.

I agree with you about adhering to a so-called standard dialect of American English for transcriptions, and I've mostly tried to stick to that. However, sometimes my linguistic ventures move me in the direction of what might result in Adidas, which, BTW has been defined in one English dictionary: https://www.ldoceonline.com/dictionary/adidas
And my today's dictionary files are attached -- yet again. I was reading a scientific article on NPR and managed to correct many pronunciations.
I'd also appreciate it if you could give me hints or suggestions regarding my ENUAbbr.dic issue.

Eloq ENU Dictionaries.zip

@amirsol81 @ultrasound1372 knows more about how the driver's cross-compatibility works, perhaps he can help you.
As for dialect, I know what you mean when you say "so-called", lol. It's going to be difficult sometimes to agree on a generic pronunciation for American English, so I appreciate that you post your sources!
I love linguistic ventures, I go on them all of the time!

@amirsol81 @ultrasound1372 knows more about how the driver's cross-compatibility works, perhaps he can help you.
As for dialect, I know what you mean when you say "so-called", lol. It's going to be difficult sometimes to agree on a generic pronunciation for American English, so I appreciate that you post your sources!
I love linguistic ventures, I go on them all of the time!

So looking forward to receiving help regarding ABBR.dic.
Good question regarding my sources. I use the following:

American Heritage Dictionary: https://ahdictionary.com
My oldest source, this used to be my favorite American Dictionary as it also shipped with the Kurzweil 1000. Unfortunately Houghton Mifflin stopped updating it in 2018, scrapping the awesome Usage Panel and the editorial team. All in all it's still an awesome resource. It offers just one audio pronunciation for each head word, and is more on the prescriptive side when it comes to audio pronunciations.
Merriam-Webster Dictionary: https://www.merriam-webster.com
This is by far the most up-to-date American English dictionary which gets updated a few times per year. It also has more words compared with AHD 5. However, its pronunciations tend to reflect the trendiest US English pronunciations available, sometimes to the point of pestering prescriptivists and conservative linguists. It offers several audio pronunciations, both for the head word and for the inflected forms, if a word happens to have more than one pronunciation.
Oxford Dictionary of American English: https://www.lexico.com/en/definition
The newest source, now offered by Lexico, Oxford Dictionary of American English also tends to get several updates per year, and offers several audio pronunciations for each head word, if available. First you should select the "Dropdown toggle" link, select US Dictionary from the list, and you are good to go. In terms of descriptivism vs prescriptivism, it sits somewhere between AHD 5 and MW. I tend to use it more frequently these days. BTW Google uses it for its display of definitions/pronunciations on its homepage, and this is the dictionary which gets installed on our iPhones with each iOS installation -- audio pronunciations are, of course, excluded. For instance -- and I know I'm rambling, with the betas of iOS 14 you can look up Covid-19 offline.
Dictionary.com: https://www.dictionary.com
This source is heavily based on the venerable RandomHouse Webster's Unabridged Dictionary which RandomHouse stopped updating in early 2000s. Dictionary.com keeps updating its database, but to me it seems more of an avocation as far as serious lexicography is concerned.
Other sources: I infrequently check Cambridge and Longman dictionaries -- their audio pronunciations for American English are eye-opening sometimes. I also tend to see how NPR hosts and hostesses pronounce terms which require more research on my part.

It was actually @Mohamed00 who made the change for that, in fact it was to be compatible with that K1000 SAPI4 driver. Maybe ECI 6.1 doesn't actually support loading these? Or we're passing it the wrong number? Or maybe it's wrongly formatted? I don't know. I'm no master of the API. And as far as the General American pronunciation of things goes, I think the exception that has been demonstrated is proper nouns, like names. Things like Uzbekistan/Pakistan, etc. But yeah, things like those will always be up for debate, as there may be an Americanization of the name and then we have to decide. I'll write up a python script at some point to prepare this kind of stuff for merging, going over a baseline and an extension dictionary and finding entries in one and not in the other and merging those, and printing some output regarding entries that are in both and showing their differences in SPRs. I think in the roots dictionary everything is supposed to be lowercase though, so I might use .lower on everything.

It does support loading the dictionaries, and at least here, enuabbr.dic seems to load properly in NVDA and SAPI4. For SAPI4, you need to put the dictionaries in your user account's folder in the Eloquence directory. If you don't see it, try registering the *.UIL files using regsvr32 while  running as administrator.

It does support loading the dictionaries, and at least here, enuabbr.dic seems to load properly in NVDA and SAPI4. For SAPI4, you need to put the dictionaries in your user account's folder in the Eloquence directory. If you don't see it, try registering the *.UIL files using regsvr32 while running as administrator.

If possible, please kindly send me your working version of ENUAbbr or ABBR, or attach it to your next reply. Here both ENUMain and ENURoot work flawlessly with both NVDA and the K1000, but ABBR.dic doesn't no matter what I do. Maybe I'm using wrong rules there -- don't know. That's why I want to test both with your ABBR/ENUAbbr file.
Thanks.

... And as far as the General American pronunciation of things goes, I think the exception that has been demonstrated is proper nouns, like names. Things like Uzbekistan/Pakistan, etc. But yeah, things like those will always be up for debate, as there may be an Americanization of the name and then we have to decide. I'll write up a python script at some point to prepare this kind of stuff for merging, going over a baseline and an extension dictionary and finding entries in one and not in the other and merging those, and printing some output regarding entries that are in both and showing their differences in SPRs. I think in the roots dictionary everything is supposed to be lowercase though, so I might use .lower on everything.

You are right about the use of lowercase letters in ENURoot.txt -- in fact, even if we paste or type all-uppercase words there, EloqTalk.EXE converts them into lowercase letters upon saving them in ENURoot.txt. Here I use EloqTalk.EXE, as part of the Eloquence SAPI 4 bundle, to correct and save mispronounced words. Its SPR from KEY and SPR from Root functions are invaluable.

Here's a quick test dictionary that works here, both with SAPI4 and NVDA. Note that you can't put phonemes or any other annotations in abbreviation dictionary entries.
enuabbr.zip

Guys, I just took a closer look at the root.dic file provided in this project, and have the following comments:

I'm a bit concerned about the inclusion of 2 or 3-letter words (like "ios" , "aly" or "os") there. I think they belong to Main.dic or even Abbr.dic. But more important than that, words like these, when corrected, tend to interfere with the pronunciation of other words. I've seen it many times myself so if you take a look at my own Root file, you might find some words whose pronunciations are correct but are included there as a result of the correction of some other words. By the same token, words like "nvda" and "nvaccess" should be moved to Main.dic as they can be better corrected/pronounced there.
The file corrects the word "formulae" as `[1fcrmyx2le]. However, it needs no correction as the proper pronunciation is provided by Eloquence -- like "antennae".
The words "aviatrix" and "aviatrices" are, IMHO, corrected erroneously -- or maybe some dialect variation is involved. I've corrected them myself and have looked them up in many dictionaries. So they should be corrected this way:
aviatrix=[.2e.0vi.1e.2trIks] aviatrices=[.2e.0vi.1e.0trX.0siz]
The word "fijian" doesn't need a correction as the one Eloquence provides is listed first in many sources.
A small point: I think the word "tranquiline" should be corrected this way -- I mean the "X" beofre "n" should be uppercase: `[.1trAG.0kwX.0lXn]
This one might require lots of discussion, but I think, and based on my own extensive investigation, the word "hyundai" should be corrected this way: `[.1hHn.0de]
And, last but not least, thanks for the file! I learned a lot from it, and have incorporated many of its terms into my own file. I'll send my own files later today.

Here's a quick test dictionary that works here, both with SAPI4 and NVDA. Note that you can't put phonemes or any other annotations in abbreviation dictionary entries.
enuabbr.zip

Thanks! I'll take a look in a few minutes.

Here's a quick test dictionary that works here, both with SAPI4 and NVDA. Note that you can't put phonemes or any other annotations in abbreviation dictionary entries.
enuabbr.zip

Thanks. It works. But it seems to me that you can'T say, correct WHO as W H O in ABBR.dic -- only "World Health Organization" is accepted. Based on this observation, I think most of my corrected abbreviations still belong to Main.dic as I simply want most of them spelled -- WAMU, WHO, and ACT, for instance.

Guys, I just took a closer look at the root.dic file provided in this project, and have the following comments:

I'm a bit concerned about the inclusion of 2 or 3-letter words (like "ios" , "aly" or "os") there. I think they belong to Main.dic or even Abbr.dic. But more important than that, words like these, when corrected, tend to interfere with the pronunciation of other words. I've seen it many times myself so if you take a look at my own Root file, you might find some words whose pronunciations are correct but are included there as a result of the correction of some other words. By the same token, words like "nvda" and "nvaccess" should be moved to Main.dic as they can be better corrected/pronounced there.
The file corrects the word "formulae" as `[1fcrmyx2le]. However, it needs no correction as the proper pronunciation is provided by Eloquence -- like "antennae".
The words "aviatrix" and "aviatrices" are, IMHO, corrected erroneously -- or maybe some dialect variation is involved. I've corrected them myself and have looked them up in many dictionaries. So they should be corrected this way:
aviatrix=[.2e.0vi.1e.2trIks] aviatrices=[.2e.0vi.1e.0trX.0siz]
The word "fijian" doesn't need a correction as the one Eloquence provides is listed first in many sources.
A small point: I think the word "tranquiline" should be corrected this way -- I mean the "X" beofre "n" should be uppercase: `[.1trAG.0kwX.0lXn]
This one might require lots of discussion, but I think, and based on my own extensive investigation, the word "hyundai" should be corrected this way: `[.1hHn.0de]
And, last but not least, thanks for the file! I learned a lot from it, and have incorporated many of its terms into my own file. I'll send my own files later today.

One more point regarding Root.dic provided in this project:
It corrects the word "superfruit", but doesn't do it for "superfruits". When the prefix "super-" is involved, the plural forms should also be corrected -- there are exceptions like this in Eloquence.

The same is true about "superfood" -- see number 8 above.
The word "dawnsinger" has been erroneously corrected as `[d1Cns2IGR]. The "c" should be lowercase as it will generate a non-pronunciation.
The word "pontes" has been corrected [p1cntes]. However, "pontes", the plural of "pons", should be corrected this way: [.1pan.2tiz].
The non-word "grandure" is corrected but I think the intended word has been "grandeur". The same can be said about the so-called non-word "panicy" -- without "k".

Folks, Having understood the ins and outs of ABBR.dic and having analyzed Root.dic provided by this project, I managed to create an Abbr.dic file with entries such as XV/XII. I also updated my Main.dic file with a few entries mostly taken from the Main.dic provided here. However, my Root.dic my Root.dic file received the most significant updates today. Some were taken from this project's Root.dic, and many more terms were added based on my own readings here and there. And while I was there, I managed to alter some of the Proper Nouns, including Adidas, to reflect the most generalized/Americanized pronunciations. I'm attaching all of them here.
Eloq ENU Dictionaries - Jul 10.zip
Thanks.

New word. SUSE. This is actually pronounced [s1usx], not [s1uz], according to this musical on SUSE's YouTube channel.

So @amirsol81 have you effectively completed the merge? And yes, acronyms like ios, nvda, nvaccess etc should be in main.dic. Those are leftovers from the very beginnings of this dictionary a few years ago when we didn't even know about how the main worked. Aly is a name. Can you name a place where it would cause a false replacement? I haven't seen any broken replacements of os myself, except when part of an acronym that is pluralized, ISOs, but wouldn't that remain the same if it weren't there? It probably goes in main, I might end up removing some of those anyways as the only reason they're there is because Mason and I originally put them there because he had started putting them there for people who erroniously did not capitalize properly. OS, NVDA, NVAccess etc.

@ultrasound1372 I was a bit concerned about the influence of the
corrected word "aly" on words like "Italy". However, performing a
wildcard search in AHD 5 indicates that "aly" hasn't altered the
pronunciation of other words so it seems to be safe to maintain it.
As for moving some entries to Main.dic, I also agree with you. In
fact, I'm doing it here and have moved many such words to ENUmain.dic.
Unfortunately Main.dic doesn't accept apostrophes. On a rather similar
topic, I'm also wondering if Main.dic or Abbr.dic can allow us to fix
words like CEOs, SMAs, FAQs, etc. I know the singular forms can be
fixed, but it seems that taking care of plural forms with that
lowercase "s" is out of the question.
As for merging the Roots, over the last 2 days I added even more terms
from the Root file provided here to my Root file. I also used the
general American pronunciation for some of my terms which tended to
have more of a non-American flavor -- terms like Volkswagen. Adidas
has taught me interesting lessons . However, the project Root
file still contains terms which I haven't yet moved to my own Root
file -- words like painspren, hungerspren, gloryspren, liespren,
exhaustionspren, etc., which sound German, Dutch or Finnish to me.
Should I integrate them? I'd say we have 70 to 80 percent of the merge
complete, but there's still some work to do on that regard. And
speaking of the merge, I'll be sending my latest files to you later
today.
PS.: Meagan is also corrected via Root.
On 7/12/20, Colton Hill<EMAIL_ADDRESS>wrote:

So @amirsol81 have you effectively completed the merge? And yes, acronyms
like ios, nvda, nvaccess etc should be in main.dic. Those are leftovers from
the very beginnings of this dictionary a few years ago when we didn't even
know about how the main worked. Aly is a name. Can you name a place where it
would cause a false replacement? I haven't seen any broken replacements of
os myself, except when part of an acronym that is pluralized, ISOs, but
wouldn't that remain the same if it weren't there? It probably goes in main,
I might end up removing some of those anyways as the only reason they're
there is because Mason and I originally put them there because he had
started putting them there for people who erroniously did not capitalize
properly. OS, NVDA, NVAccess etc.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657176169

BTW the project Root file has corrected the word "babel" whereas I
have retained the original. Speaking of such corrections, I have
corrected "rasputin" as [.0rAs.1pyu.0tXn] based on American Heritage 5th and Merriam-Webster, but the one provided by the project is [r1aspu2tin] which sounds a bit non-English. What should we do with
those two?
On 7/12/20, Amir Soleimani<EMAIL_ADDRESS>wrote:

@ultrasound1372 I was a bit concerned about the influence of the
corrected word "aly" on words like "Italy". However, performing a
wildcard search in AHD 5 indicates that "aly" hasn't altered the
pronunciation of other words so it seems to be safe to maintain it.
As for moving some entries to Main.dic, I also agree with you. In
fact, I'm doing it here and have moved many such words to ENUmain.dic.
Unfortunately Main.dic doesn't accept apostrophes. On a rather similar
topic, I'm also wondering if Main.dic or Abbr.dic can allow us to fix
words like CEOs, SMAs, FAQs, etc. I know the singular forms can be
fixed, but it seems that taking care of plural forms with that
lowercase "s" is out of the question.
As for merging the Roots, over the last 2 days I added even more terms
from the Root file provided here to my Root file. I also used the
general American pronunciation for some of my terms which tended to
have more of a non-American flavor -- terms like Volkswagen. Adidas
has taught me interesting lessons . However, the project Root
file still contains terms which I haven't yet moved to my own Root
file -- words like painspren, hungerspren, gloryspren, liespren,
exhaustionspren, etc., which sound German, Dutch or Finnish to me.
Should I integrate them? I'd say we have 70 to 80 percent of the merge
complete, but there's still some work to do on that regard. And
speaking of the merge, I'll be sending my latest files to you later
today.
PS.: Meagan is also corrected via Root.
On 7/12/20, Colton Hill<EMAIL_ADDRESS>wrote:

So @amirsol81 have you effectively completed the merge? And yes, acronyms
like ios, nvda, nvaccess etc should be in main.dic. Those are leftovers
from
the very beginnings of this dictionary a few years ago when we didn't
even
know about how the main worked. Aly is a name. Can you name a place where
it
would cause a false replacement? I haven't seen any broken replacements
of
os myself, except when part of an acronym that is pluralized, ISOs, but
wouldn't that remain the same if it weren't there? It probably goes in
main,
I might end up removing some of those anyways as the only reason they're
there is because Mason and I originally put them there because he had
started putting them there for people who erroniously did not capitalize
properly. OS, NVDA, NVAccess etc.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657176169

The words "aviatrix" and "aviatrices" are, IMHO, corrected erroneously -- or maybe some dialect variation is involved. I've corrected them myself and have looked them up in many dictionaries. So they should be corrected this way:
aviatrix=[.2e.0vi.1e.2trIks] aviatrices=[.2e.0vi.1e.0trX.0siz]

The word "fijian" doesn't need a correction as the one Eloquence provides is listed first in many sources.

I can see why you would use `[e] here in aviatrix/ces, although is the stress really there? As for the plural form, I think I misinterpreted or just got carried away with Latin, see similar words that end in "x" and pluralise with "ces".
I'm not sure I fully agree on Fijian, eloquence's default pronunciation is `[.1fI.0Ji.0Xn], which doesn't even sound like it has anything to do with Fiji. I live not too far from those islands, so perhaps I have a dialectal bias, but all Americans I've spoken to pronounce it to rime with "Aegean", sometimes with the stress on the first syllable.

However, the project Root file still contains terms which I haven't yet moved to my own Root file -- words like painspren, hungerspren, gloryspren, liespren, exhaustionspren, etc., which sound German, Dutch or Finnish to me. Should I integrate them? I'd say we have 70 to 80 percent of the merge complete, but there's still some work to do on that regard. And speaking of the merge, I'll be sending my latest files to you later today. PS.: Meagan is also corrected via Root.

The "-spren" words are from a fantasy series written in English, I had to add them all individually because regexp in the dictionaries is sadly not a thing, at least to my knowledge. It would be good to include them and probably safe, I can't at the moment think of any suffix conflicts.
Thanks for your feedback and the awesome work you're doing :D

Please let us know when you've finished what you consider to be a full merge, there are some omissions in this version and a few blatant errors in your file that I'd want to discuss and correct, but obviously when we're all on the same page.

The words "aviatrix" and "aviatrices" are, IMHO, corrected erroneously -- or maybe some dialect variation is involved. I've corrected them myself and have looked them up in many dictionaries. So they should be corrected this way:
aviatrix=[.2e.0vi.1e.2trIks] aviatrices=[.2e.0vi.1e.0trX.0siz]

The word "fijian" doesn't need a correction as the one Eloquence provides is listed first in many sources.

I understand and mostly agree with 3, my thinking was along the lines of "index"/"indices", "matrix"/"matrices", etc.
I have never heard anyone say Fijian the way Eloquence says it, and not just because I live near those islands. Most Americans I have heard say the word pronounce it to rhyme with "Aegean", sometimes with stress on the first syllable, rather than the second.
I do agree on "tranquiline".

However, the project Root
file still contains terms which I haven't yet moved to my own Root
file -- words like painspren, hungerspren, gloryspren, liespren,
exhaustionspren, etc., which sound German, Dutch or Finnish to me.
Should I integrate them? I'd say we have 70 to 80 percent of the merge
complete, but there's still some work to do on that regard.

Absolutely everything that is in the existing project root should be included in the project going forward, unless it can cause technical error, like you mentioned above. Those specific words are from a fantasy series written in English by an American author. I wish we could have regexps in the dictionary!
Please let us know when you've finished what you consider to be a full merge, there are some omissions in this version and a few blatant errors in your file that I'd want to discuss and correct, but obviously when we're all on the same page. I say "a few blatant errors" because I haven't looked at every one of your twenty-five thousand-odd entries, but even at a glance, some things stick out to me as a linguist and fellow long-time user of Eloquence.
E.G. In general American English, the "a" in "water" is a /ɔ/ or sometimes a /ɔː/, transcribed in all cases as [c]. In the word waterbed, you have used an /ɑ/ ([a]), which is incorrect.
"Linux" is, and always has been pronounced the way that eloquence does, with a schwa. This really isn't the controversy people think it is, here's a video of it's inventor pronouncing it. In my opinion, the inventor of a word should be considered the definitive source on such things as pronunciation, until such time that the word becomes so commonly used that it naturally develops dialectal variation.
These may seem like picking, I'm sorry if they do. I honestly don't intend anything like that, these are just examples and things to think about. The first I encountered almost at the top of the dictionary, and it stuck in my mind. The second stuck out to me because I work closely with Linux systems and it was like a jab in the skull.
This merge may take a bit longer than expected, there are many words to go through, and sources to consider. I'm finding the dictionaries pretty consistent and functional so far, but perhaps more of a test drive is required. I know a few people who would chew on us pretty thoroughly for giving them lin-ucks.

Interestingly, in Eloquence 5, Linux use to be pronounced [l1InHks], but
it seems IBM corrected it and the correction filtered down at some point.
On 7/12/2020 8:44 AM, Peregryn Winterwell wrote:

 3. The words "aviatrix" and "aviatrices" are, IMHO, corrected
    erroneously -- or maybe some dialect variation is involved.
    I've corrected them myself and have looked them up in many
    dictionaries. So they should be corrected this way:
    aviatrix=[.2e.0vi.1e.2trIks] aviatrices=[.2e.0vi.1e.0trX.0siz]

The word "fijian" doesn't need a correction as the one Eloquence
provides is listed first in many sources.

I understand and mostly agree with 3, my thinking was along the lines
of "index"/"indices", "matrix"/"matrices", etc.
I have never heard anyone say Fijian the way Eloquence says it, and
not just because I live near those islands. Most Americans I have
heard say the word pronounce it to rhyme with "Aegean", sometimes with
stress on the first syllable, rather than the second.
I do agree on "tranquiline".
However, the project Root
file still contains terms which I haven't yet moved to my own Root
file -- words like painspren, hungerspren, gloryspren, liespren,
exhaustionspren, etc., which sound German, Dutch or Finnish to me.
Should I integrate them? I'd say we have 70 to 80 percent of the merge
complete, but there's still some work to do on that regard.

Absolutely everything that is in the existing project root should be
included in the project going forward, unless it can cause technical
error, like you mentioned above. Those specific words are from a
fantasy series written in English by an American author. I wish we
could have regexps in the dictionary!
Please let us know when you've finished what you consider to be a full
merge, there are some omissions in this version and a few blatant
errors in your file that I'd want to discuss and correct, but
obviously when we're all on the same page. I say "a few blatant
errors" because I haven't looked at every one of your twenty-five
thousand-odd entries, but even at a glance, some things stick out to
me as a linguist and fellow long-time user of Eloquence.
E.G. In general American English, the "a" in "water" is a /ɔ/ or
sometimes a /ɔː/, transcribed in all cases as |[c]. In the word
waterbed, you have used an /ɑ/ (|[a]), which is incorrect.
"Linux" is, and always has been pronounced the way that eloquence
does, with a schwa. This really isn't the controversy people think it
is, here's a video https://www.youtube.com/watch?v=5IfHm6R5le0 of
it's inventor pronouncing it. In my opinion, the inventor of a word
should be considered the definitive source on such things as
pronunciation, until such time that the word becomes so commonly used
that it naturally develops dialectal variation.
These may seem like picking, I'm sorry if they do. I honestly don't
intend anything like that, these are just examples and things to think
about. The first I encountered almost at the top of the dictionary,
and it stuck in my mind. The second stuck out to me because I work
closely with Linux systems and it was like a jab in the skull.
This merge may take a bit longer than expected, there are many words
to go through, and sources to consider. I'm finding the dictionaries
pretty consistent and functional so far, but perhaps more of a test
drive is required. I know a few people who would chew on us pretty
thoroughly for giving them lin-ucks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657217085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADY4AYBJWI2IYWOGUWHP2ELR3GV2ZANCNFSM4OMPYM5Q.

Another issue I found with this dictionary. You've chosen to pronounce dos as `[.1duz], I suppose for things like dos and don'ts, however this breaks MS-DOS.

Another issue I found with this dictionary. You've chosen to pronounce dos as `[.1duz], I suppose for things like dos and don'ts, however this breaks phrases like "DOS prompt" and "boot into DOS".

You are right -- dos and don'ts. However, a couple of days ago I did the same thing to "DOS" in ENUmain.dic to take care of it. I'll be sending them here. ENUmain.dic adds a lot of flexibility to what we are doing.

@thunderdrop I fully agree with you regarding Linux as your argument is what I have long advocated myself. For Linux I decided to go with what American Heritage Dictionary 5 suggests, but I'll remove it. I'll also include "Fijian" the way you proposed although it is listed second in many dictionaries. Of course the way Eloquences the first syllable is problematic regardless of the suggested pronunciation. You kindly suggested a couple of more points which I haven't managed to digest, but I'll be taking a closer look at them shortly.
Thanks.

@thunderdrop I see your point regarding "waterbed". However, it's a so-called "slip of the finger" I suppose because I'm well aware of the rule you mentioned and have frequently utilized it in my corrections. I do welcome your awesome analysis and observation, though.

Glad to see all the progress. I've been kinda hands-off lately, sorry about that, though I'm relieved that you're handling the merge yourself because I haven't written that python script yet :). So main allows for case stuff so DOS and dos get pronounced separately? Also can we do anything about don'ts? Default eloquence pronounces it with an a, when it should be an o, but I'm not sure about that apostrophe getting in the way. If it can be corrected via root make sure you only correct the plural form, if you try and correct the singular and have it propogate you'll break function word detection, as eloquence doesn't let us specify in the English dictionaries what part of speech a given word is.

I can confirm that Eloquence does allow apostrophes in root dictionary
entries, found this out while I was correcting O'shaughnessy, though I
learned that the o' is unnecessary in the root entry. Fixing don'ts
shouldn't be an issue, and if it breaks a word we can just enter it and
that variant will be overwritten.
On 7/12/2020 4:56 PM, Colton Hill wrote:

Glad to see all the progress. I've been kinda hands-off lately, sorry
about that, though I'm relieved that you're handling the merge
yourself because I haven't written that python script yet :). So main
allows for case stuff so DOS and dos get pronounced separately? Also
can we do anything about don'ts? Default eloquence pronounces it with
an a, when it should be an o, but I'm not sure about that apostrophe
getting in the way. If it can be corrected via root make sure you only
correct the plural form, if you try and correct the singular and have
it propogate you'll break function word detection, as eloquence
doesn't let us specify in the English dictionaries what part of speech
a given word is.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657273896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADY4AYAQOSXALK3WIN7TRPLR3IPOVANCNFSM4OMPYM5Q.

Glad to see all the progress. I've been kinda hands-off lately, sorry about that, though I'm relieved that you're handling the merge yourself because I haven't written that python script yet :). So main allows for case stuff so DOS and dos get pronounced separately? Also can we do anything about don'ts? Default eloquence pronounces it with an a, when it should be an o, but I'm not sure about that apostrophe getting in the way. If it can be corrected via root make sure you only correct the plural form, if you try and correct the singular and have it propogate you'll break function word detection, as eloquence doesn't let us specify in the English dictionaries what part of speech a given word is.

Thanks. It's quite a challenge, but I'm trying to get it done. It is a bit complicated because if I add a term to the dictionary and it already exists, EloqTalk will remove both. In addition, some terms exist in the project Root which, to me, sound like either misspelled words or already correct and I'm leaving the decision to include them to you -- words like "misshape" and "misshape" which are correct and don't need to be included, the word "descarte" which has been added without its final "s", and a couple of British English spellings ending in "ise" which have been corrected by placing stress on the wrong syllable.
As for Main.dic, it provides us with an extra layer of flexibility and can distinguish between uppercase and lowercase, and even capitalized words.

Thanks. It's quite a challenge, but I'm trying to get it done. It is a bit complicated because if I add a term to the dictionary and it already exists, EloqTalk will remove both. In addition, some terms exist in the project Root which, to me, sound like either misspelled words or already correct and I'm leaving the decision to include them to you -- words like "misshape" and "misshape" which are correct and don't need to be included, the word "descarte" which has been added without its final "s", and a couple of British English spellings ending in "ise" which have been corrected by placing stress on the wrong syllable.
As for Main.dic, it provides us with an extra layer of flexibility and can distinguish between uppercase and lowercase, and even capitalized words.

I'd like to re-iterate that everything that was already in the project file should be in the project going forward, unless it causes a technical error. The misspellings are fully intentional, some were added from MUDs, books, and forums. Although you're right about the -ise words, I was running into some pronunciation inconsistencies between British and American English spellings, and fixed them badly. I never got around to doing them properly until now, so  I can fix those.
I appreciate Main, and agree that it'll be more useful for us in many situations.
Also, Amir, I wanted to apologise if I have come across as condescending in public comments to you. I'm not meaning to tell you things you already know, but provide the information to anyone reading this who isn't so familiar with how phonetics work I hope you can forgive a bit of the tedium, I just like to clarify things. Old habit from writing documentation.

Folks, the merge is effectively complete, and what a feat! 😀
All misspelled words are also included although I don't like them much as they might serve to mislead people who rely on something like Eloquence for learning.
Anyway, before sending the dictionary files to the list, let me ask some questions:

The word "gingey" has been corrected as `[J1Inji]. However, this seems to be a problematic correction as Eloquence has difficulty pronouncing it.
The word "refill" has been corrected as [r1ifIl]. However, this just reflects its noun form. I myself had corrected it as [.0ri.1fIl] to reflect the verb form and its inflections. Obviously the original Eloquence pronunciation is wrong so we should decide which pronunciation to add. I suggest to correct it for its verbal function but am open to suggestions.
The word "infographic" has been corrected to stress the first syllable. However, what Eloquence pronounces is reflected by many dictionaries so I haven't included it yet. Here's one example based on Oxford Dictionary of American English: https://www.lexico.com/en/definition/infographic
I have no clue, but does the word "ojban" has an "l" in it? `[1loZ2ban]
By the same token, the word "taranaki" has a "t-like" consonant in its correction instead of "r". `[t1aFxnaki]. Is this correct?
The same is true about the word "wiremu" and its correction `[w1IFxm2u]. How about this one?
I've heard different pronunciations for the famous "tiananmen" square, and most of them stress the "men" syllable. However, the project Root file corrects it as `[ty1EnXnMxn]. Any thoughts?
Both Oxford and Merriam-Webster suggest the following pronunciation for the word "antinomy": `[.2An.1tI.0nx.0mi]. But the root file corrects it in a different way -- I don't have it at the moment but think it stresses the "no" syllable. BTW its plural form should also be corrected because of the effect of the prefix "anti-". So should I retain my correction for this and its plural form?
Of course, having asked all of these, I can send the files to you so that you can make the remaining changes if you wish. I've also made many correction to my own entries but am dead sure more than 25,000 entries require many suggestions and changes on your part -- @thunderdrop do you hear me? 😂

Also, Amir, I wanted to apologise if I have come across as condescending in public comments to you. I'm not meaning to tell you things you already know, but provide the information to anyone reading this who isn't so familiar with how phonetics work. I hope you can forgive a bit of the tedium, I just like to clarify things. Old habit from writing documentation. Thanks for all of your help!

@thunderdrop No problem at all -- I love these discussions. In fact, had I disliked such comments, I wouldn't have provided my own Gargantuan Root file as it sure instigates a lot of discussion, and something should be wrong with me if I assume that it needs zero corrections!
My only minor gripe, if you can call it a gripe anyway, with the current project is the inclusion of some obviously misspelled words. My TEFL/TESL side is definitely responsible for this nitpicking, but I think if we include Descarte without S, Panicy without k, grandeuer with E and U misplaced, etc., we'll generate false positives. After all, many people might rely on Eloquence to improve their spelling -- the way I did and am still doing. Moreover, no TTS engine pronounces these misspelled words properly. I've included them to comply with your request and understand how they might facilitate reading, but my reservations still remain.

I'll jump in and say I agree with Amir here and I think that the
misspellings should be removed. The last thing we should do is feed the
stereotype that Eloquence users can't spell.
On 7/13/2020 11:56 AM, amirsol81 wrote:

Also, Amir, I wanted to apologise if I have come across as
condescending in public comments to you. I'm not meaning to tell
you things you already know, but provide the information to anyone
reading this who isn't so familiar with how phonetics work. I hope
you can forgive a bit of the tedium, I just like to clarify
things. Old habit from writing documentation. Thanks for all of
your help!

@thunderdrop https://github.com/thunderdrop No problem at all -- I
love these discussions. In fact, had I disliked such comments, I
wouldn't have provided my own Gargantuan Root file as it sure
instigates a lot of discussion, and something should be wrong with me
if I assume that it needs zero corrections!
My only minor gripe, if you can call it a gripe anyway, with the
current project is the inclusion of some obviously misspelled words.
My TEFL/TESL side is definitely responsible for this nitpicking, but I
think if we include Descarte without S, Panicy without k, grandeuer
with E and U misplaced, etc., we'll generate false positives. After
all, many people might rely on Eloquence to improve their spelling --
the way I did and am still doing. Moreover, no TTS engine pronounces
these misspelled words properly. I've included them to comply with
your request and understand how they might facilitate reading, but my
reservations still remain.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657643047,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADY4AYH7RSOVNYDCH7Q4DADR3MVBPANCNFSM4OMPYM5Q.

@amirsol81 @Mohamed00 I don't fully understand your thinking here, admittedly on an intellectual level. If someone is worried about their spelling, then they can become a better speller by finding out how words are spelt. English orthography is so irregular that this is practically necessary, because pronunciation hardly reflects spelling.
Text to speech was never designed with spelling  alone in mind. A user will always be able to misspell something and have it pronounced correctly, my favourite example is spelling "chicken" as "czyhqun". I thought that rather than break the immersion of reading something just to pick at someone's spelling skills was not really the job of the TTS engine; If someone wants to put all of that energy into judging someone, then they can put that energy into reading it manually.
All of that snark aside, we could be here for years trying to incorporate every possible misspelling, so for the purposes of public release, I agree with both of you. We shouldn't include them, and if it bothers an individual, then they have their own pronunciation dictionaries for things like that.
Amir, I'm working on your list of questions above, I'll put my suggestions/answers in a comment below. Thanks for doing the mega-merge! :D

Your points regarding spelling and TTS engines are well taken. However, at
least as far as writing is concerned, I have seen people, especially
non-Native speakers, Who tend to rely on what their TTS engines pronounce
to decide if they have typed correctly. I don’t want to read or Dell too
much into that argument, but it is my humble opinion that we should avoid
including obvious mispronunciations unless they have found their way into
major American English dictionaries. Just my two cents…
On Tue, Jul 14, 2020 at 00:12 Peregryn Winterwell<EMAIL_ADDRESS>wrote:

@amirsol81 https://github.com/amirsol81 @Mohamed00
https://github.com/Mohamed00 I don't fully understand your thinking
here, admittedly on an intellectual level. If someone is worried about
their spelling, then they can become a better speller by finding out how
words are spelt. English orthography is so irregular that this is
practically necessary, because pronunciation hardly reflects spelling.
Text to speech was never designed with spelling alone in mind. A user will
always be able to misspell something and have it pronounced correctly, my
favourite example is spelling "chicken" as "czyhqun". I thought that rather
than break the immersion of reading something just to pick at someone's
spelling skills was not really the job of the TTS engine; If someone wants
to put all of that energy into judging someone, then they can put that
energy into reading it manually.
All of that snark aside, we could be here for years trying to incorporate
every possible misspelling, so for the purposes of public release, I agree
with both of you. We shouldn't include them, and if it bothers an
individual, then they have their own pronunciation dictionaries for things
like that.
Amir, I'm working on your list of questions above, I'll put my
suggestions/answers in a comment below. Thanks for doing the mega-merge! :D
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657754066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIGLZMQPM3AVKIAJUSOUAYLR3NPS5ANCNFSM4OMPYM5Q
.

--
Sent from Gmail Mobile via iPhone

Your points regarding spelling and TTS engines are well taken. However, at least as far as writing is concerned, I have seen people, especially non-Native speakers, Who tend to rely on what their TTS engines pronounce to decide if they have typed correctly. I don’t want to read or Dell too much into that argument, but it is my humble opinion that we should avoid including obvious mispronunciations unless they have found their way into major American English dictionaries. Just my two cents…

This is true. As a polyglot, I can definitely appreciate the need for semi-consistent TTS pronunciations, I think it's probably just been my privilege to have learnt languages with consistent letter-to-sound rules. I feel for non-native speakers, and agree with your ideas. Thanks for the perspective.

@thunderdrop You are most welcome!
While awaiting your comments on the words I queried yesterday, let me
ask about a few more as I went through the Root file provided here
once again:

The Root file fixes the word "quim" as `[k1im]. However, I've heard
it with "w", both similar to how Eloquence pronounces it and the way
AHD 5 and Merriam-Webster pronounce it. What do you think?
The file fixes the word "halsey" as [h1Alzi]. However, many sources prefer, and actually suggest, [.1hcl.0zi]. So what to do?
The file fixes "sequoia" as [sXk1Ox]. However, everywhere I've checked, the following is recommended: [.0sX.1kwY.0x]. Please help!
Guess I asked this before but apparently no one commented. The file
fixes the word "babel" as "babble". But I'm not sure which one is more
frequent. I haven't fixed it in my file as I've heard the original a
lot, but would appreciate your perspectives on that.
How about "rasputin"? The file fixes it as [r1aspu2tin] but, based on many dictionary recommendations and what I've heard, I had corrected it as [.0rAs.1pyu.0tXn].
The file provides the following fix for the word "exec",
emphasizing the first syllable: [1Egz2Ek]. However, all American English dictionaries and my NPR sources recommend/pronounce it as [.0Xg.1zEk]. It's getting complicated!
Should the "w" in "weiner" be pronounced as "v"? `[v1YnR]. The file
does it, and I have no clue about this one.
Finally, the file fixes "sexagenary" as [sEksxJ1EnXri][ But again what Eloquence pronounces is accordance with major American English dictionaries, so it seems that no correction is needed: [.2sEk.1sA.0JX.2ner.0i]. So what's your take on this?
That's all for now -- hopefully! Sorry for asking so many questions.  However, at
least as far as writing is concerned, I have seen people, especially
non-Native speakers, Who tend to rely on what their TTS engines pronounce
to decide if they have typed correctly. I don’t want to read or Dell too
much into that argument, but it is my humble opinion that we should avoid
including obvious mispronunciations unless they have found their way into
major American English dictionaries. Just my two cents…

This is true. As a polyglot, I can definitely appreciate the need for
semi-consistent TTS pronunciations, I think it's probably just been my
privilege to have learnt languages with consistent letter-to-sound rules. I
feel for non-native speakers, and agree with your ideas. Thanks for the
perspective.

--

You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub:

https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-657758823

@amirsol81 Hi, I've tried to answer your questions. There's no such thing as too many for a thing like this, and I'll have heaps of my own for you, so don't apologise! :-) Here goes:

"Gingey" was a personally required pronunciation at the time I added it, and can probably be omitted. Some of these are the case, I'll try and pick them out if you don't get there first!
We had someone send in a correction to "refill" and we were trying it to reflect the noun form, but I pointed out at the time that we would have to decide. Comparing that version to your version, your version just sounds more solid. I think even though it will make the noun form sound a little strange, it made the verb form stranger to have it the other way.
I wasn't aware about "infographic", people over here in NZ tend to stress the "info" part. Thank you!
"lojban" should have an l in it, whoops. The pronunciation reflects the correct spelling. Also if you don't know what lojban is I recommend you check it out, think it might be interesting to you.
The F in the transcription of Taranaki is meant to simulate the alveolar tap you hear when you say this word in Māori. Possibly not appropriate for an American dictionary, I'm just a native speaker and it was hard not to. What do people think about this?
See item 5.
Your pronunciation of "tiananmen" is closer to the way that People in Beijing say it. Mine is closer to the way people in America say it, or at least from what I've heard on news reports, audio books, etc. Both are technically incorrect, but which one to pick? Lol.
I didn't realise that the prefixes were the reason why some words need a plural correction, you've solved a mystery for me! That's probably my British English getting in the way, your correction for antinomy looks right from the brief research I just did, so I'd say use yours.
Quim is a proper noun also, it's a Portuguese name, and it's pronounced as such in Portugal and Brazil. Perhaps a case-sensitive version? Or just take it out altogether?
There was a lot of confusion and debate on social media a few years ago regarding the name Halsey, and I corrected it from the data I thought I had at the time. Some research show's you to be right about this.
I'm very confused also about the pronunciation of "sequoia", I've heard everything from my correction to yours. Yours is probably better because it has the weight of research behind it, we'll see if it causes any confusion I guess.
You did ask about "Babel", sorry about that. I think British English strikes again. I really need to look these things up first.
"Rasputin" is correct for American English, I'm just a Boney M fan and I speak a little Russian. :D
"Exec" is a complicated one. In the context of the word "executive", it should be the way eloquence pronounces it. However, often in the context of the word "executable", which I personally encounter more, you find it with the first syllable emphasised. This is why it is the way it is, any thoughts?
I think it's probably safe to have "Weiner" pronounced with a v sound, it's like "Wagner", which your file seems to correct.
"sexagenary" sounded weird and clunky, and I found a few sources at the time which said it would be okay to pronounce it the way I entered, However, I can't remember what I used and you have it right there in front of you, so I think we'll just keep it the way eloquence says it.

I think these answers may have just spawned more questions, look forward to more discussion. Thanks for contributing so much and asking such good questions.

@thunderdrop Thanks for your awesome and eye-opening reply!

So I haven't yet added the words Taranaki and wiremu. Should I do it and keep that soft "T" sound? Since you asked for opinions and I'm clueless here, I thought I'd delay their inclusion.
Thanks for the ojban link! I also added it.
I have corrected Tiananmen based on the recommendations of RandomHouse Webster's Unabridged Dictionary (now available at Dictionary.com) and American Heritage 5th Edition. But I'll change it to whatever people agree upon
As for exec, since I've encountered the phrase "company execs" a lot, I decided to change it to that variation which is recommended by American English dictionaries -- I mean the one which differs from the one provided by the project Root file. But I''ll change to whatever is suggested here.
Weiner has also been corrected based on your suggestion.
And thanks for your confirmation affecting the rest of the words!
Folks, attached is a ZIP file containing the very latest dictionary revisions -- Root, Main and Abbr. The Root file contains the merge, and you can find some entries in Main. Please take a look and let me know what you think. Also do feel free to analyze/lambaste/dissect my files! It's worth mentioning that my Root file corrects the word "Louisville" as I researched it few years ago and decided to include it based on what many dictionaries recommend. But it can be expunged if you want.
Eloq ENU Dics - Jul 14.zip

Folks, please accept my apologies. Attached is yet another ZIP archive with the same dictionary files. I had moved sndup to Main, but had forgot to remove it from Root. Moreover, I also made a couple of minor changes to Root.
Eloq ENU Dics_Rev - Jul 14.zip

Interestingly, some of these pronunciations seem to break Eloquence's de-stressing rules for specific phrases. For example, the fix for "pickup" breaks "pickup truck", and "tournament" breaks football, basketball, or breaks football, basketball, and baseball tournament. You don't have to remove it as admittedly as your pronunciation is probably a bit more correct, just an observation.

Interestingly, some of these pronunciations seem to break Eloquence's de-stressing rules for specific phrases. For example, the fix for "pickup" breaks "pickup truck", and "tournament" breaks football, basketball, or breaks football, basketball, and baseball tournament. You don't have to remove it as admittedly as your pronunciation is probably a bit more correct, just an observation.

"pickup" is a problematic pronunciation for Eloquence with its schwa. In general, Eloquence has issues with words ending in "up" without a dash -- signup, touchup, wickiup, mockup, nohup, stackup, writeup, markup, etc. So apparently it needs to be corrected.
As for tournament, it is recommended by all American English dictionaries with its tour-like pronunciation. But the "ter" is also accepted as the second pronunciation by a couple of dictionaries. That said, Eloquence's pronunciation is gaining popularity so we can revert to the original if you wish.

For the context of exec, see eval. Abbreviated function names. But I do agree that since company execs are mentioned more that that should take priority, unless we really wanted to do some possibly clunky stuff and if they never talk about one exec but do talk about multiple execs, the singular form could be CS, while the plural could be business. That would probably seem really confusing from an outsider's point of view, though. And re Louisville, we were holding off on that one because we weren't sure if it was region specific within the US to that area, which isn't what eloquence tries to sound like. If it's common enough I see no reason why it shouldn't be included.

Rasputin falls under that area of proper names as does Wagner, no? So in this case I might lean towards the way it would be pronounced in Russian. [.1rAs.0pyX.0tXn], and especially the more common American [.0rAs.1pyu.0tXn] sounds kind of... Bastardized to me.

@ultrasound1372 Quite interestingly, for Louisville all American English Dictionaries only display the minus-s sound, and the only definition they offer for it is "The largest city of Kentucky ...". Even the WaveNet Google TTS which is very good at reflecting standard American English pronunciations prefers that: https://cloud.google.com/text-to-speech
So by not including that minus-s variation we might gravitate toward something which is less commonly used and heard. Even MS OneCore prefers that, but I'll accept the consensus here.

Rasputin falls under that area of proper names as does Wagner, no? So in this case I might lean towards the way it would be pronounced in Russian. [.1rAs.0pyX.0tXn], and especially the more common American [.0rAs.1pyu.0tXn] sounds kind of... Bastardized to me.

Well, actually there exists a difference here. All American English dictionaries accept and recommend the Americanized Rasputin: .1pyu. However, the same is true about Wagner with the V sound. That is, they recommend the so-called non-American V pronunciation for Wagner, Richard  1813-1883, but suggest the American W-sounding pronunciation for Wagner, Honus 1874-1955: American baseball player who during his 21-year career (1897-1917) was consistently among the National League's best batters. This is from AHD 5. So we have two Wagners here. I can return to the original Eloquence pronunciation for it if you wish. Anyhow -- and returning to Rasputin, I suggest using the Americanized version -- like Adidas, but this is just a vote.

@amirsol81 @ultrasound1372 I think we should decide how we're going to deal with names. We seem to have Americanized some, and left others to approximations of native language pronunciation. I personally don't have too much of a problem with this, it's nice to honour pronunciations of names. But I also said waaaay above here that we should be less interested in preserving etymologies. I'm sorry if I've confused things 😂

Also I'm aware that etymologies aren't pronunciations, but they do affect them.

@amirsol81 @ultrasound1372 I think we should decide how we're going to deal with names. We seem to have Americanized some, and left others to approximations of native language pronunciation. I personally don't have too much of a problem with this, it's nice to honour pronunciations of names. But I also said waaaay above here that we should be less interested in preserving etymologies. I'm sorry if I've confused things 😂

This is both an interesting and a murky area. Having thought about it for a few days, I also think we should try to move toward Americanized pronunciations especially if they have become quite popular -- again Adidas serves as a very good case in point. However, with country and city names, things become rather cryptic. Is there a "Cow" in "Moscow"? Quite incidentally, there's a book titled "Is There a Cow in Moscow" by Charles Harrington Elster. Anyhow, I have altered Moscow because the non-cow pronunciation both reflects the original and is recommended by many American English dictionaries. It's also used frequently on NPR, PRI and APM. But one can't be certain with names like Kazakhstan, and Uzbekistan. The original, non-American pronunciations which are recommended by AHD 5 sound quite weird in American English. So I decided to go with the Oxford/Merriam versions which are both more Americanized and more popularly heard. BTW I can return to the cow-like pronunciation for Moscow if you think that's more appropriate.

@thunderdrop Also if doesn't prove to be confusing, I think we should adopt the "popularity" factor more than the American/non-American factor. So, which version of Rasputin is more popular, is heard more frequently and is recommended more often? The same is true about names of countries, capitals, brands, etc. Again sticking to Rasputin, some non-American pronunciations aren't popular and sound a bit strange. But returning to Adidas, some Americanized pronunciations have become so popular that we can't simply ignore them for the sake of sticking to the American vs. non-American patterns. I know this is also confusing, so maybe we should discuss these one by one, check their popularities, consult dictionaries, etc etc.

@amirsol81 I agree with that. It's a strange way of thinking for me, because as a linguist and polyglot I love to pronounce words the way they were intended to be pronounced in their native language. But I see the merit in consistency, and think popularity is probably the best way to go. I'd like to find out how some dictionaries collect their pronunciation data, though. When we ask what the more popular pronunciation is, to whom is it more popular? Which communities have been sampled? I know you're not responsible for that,  it's just an interesting thing to think about. You work more closely with English than I do in a few ways, do you teach general pronunciation by the dictionary? I'm curious.

@amirsol81 I agree with that. It's a strange way of thinking for me, because as a linguist and polyglot I love to pronounce words the way they were intended to be pronounced in their native language. But I see the merit in consistency, and think popularity is probably the best way to go. I'd like to find out how some dictionaries collect their pronunciation data, though. When we ask what the more popular pronunciation is, to whom is it more popular? Which communities have been sampled? I know you're not responsible for that, it's just an interesting thing to think about. You work more closely with English than I do in a few ways, do you teach general pronunciation by the dictionary? I'm curious.

Very interesting questions. Of course, we can never get definitive answers from them other than some very generalized assumptions -- stuff which we expect dictionary publishers to subscribe to. For instance, Merriam-Webster provides the following answer -- via this PDF file and I quote: https://www.merriam-webster.com/assets/mw/static/pdf/help/guide-to-pronunciation.pdf
""The pronunciations in this dictionary are informed chiefly by the Merriam-Webster pronunciation file. This file contains citations that are transcriptions of words used by native speakers of English in the course of utterances heard in speeches, interviews, and conversations. In this extensive collection of 3 × 5 slips of paper, one finds the pronunciations of a host of people: politicians, professors, curators, artists, musicians, doctors, engineers, preachers, activists, journalists, and many others. The Merriam-Webster pronunciation editors have been collecting these citations from live speech and from radio, television, and shortwave broadcasts since the 1930s. It is primarily on the basis of this large and growing file that questions of usage and acceptability in pronunciation are answered. All of the pronunciations recorded in this book can be documented as falling within the range of generally acceptable variation, unless they are accompanied by a restricting usage note or symbol or a regional label."
On the other hand, dictionary-making in the USA is almost dead -- with the prime exceptions of MW and Oxford -- the latter still updates the American version quite actively. So even my beloved AHD 5 which stopped being updated in 2018 by Houghton Mifflin can't be fully trusted in terms of pronunciations especially as time goes by. Random House also kissed goodbye to dictionary-making in early 2000s, so its pronunciations, offered on Dictionary.com, should be accepted with a questionable grain of salt.
I'm more of a radio journalist rather than an English instructor although I still teach English from time to time. But I love languages, and find English (especially the North American variation) quite intriguing and attractive as someone who lives on this side of the pond.

@thunderdrop I used to include the words "transient" and "transience" to accept the "sh"-like pronunciations: so transient would rhyme with ancient. But when I saw that everyone is saying tranZEE-unsand dictionaries recommend it, I reverted to the original Eloquence pronunciations. I myself prefer, and actually use, the ancient-rhyming variation, but when it comes to Root.dic/Main.dic, I'm not in a position to promote traditional/original pronunciations.-

@amirsol81 Oh yes, I hear you on that! Thanks for the information about Merriam-Webster, I'll do some digging on my own because I'm curious about representation.
I'm using your merged file now, and I encourage everyone to grab that and try it out, as it resembles what the August 1 release will be like. No doubt questions and corrections will come up, but that's why this project is here. Thanks for offering your experience and for your hard work, I hope you stick around!

@thunderdrop You are most welcome -- such a great honor!
I also suggest that people use my files. Till August 1st I'll do my
best to make the needed changes/corrections. For instance, here's what
I've done today -- so far:

Removed "tournament" as the non-tour pronunciation is
popular/recommended enough.
Added the word "Whitaker".
Added the word "abuser" as Eloquence mispronounces it in
combination with other words such as "sex abuser". "z" is incorrectly
pronounced as "s" in such combinations.

On 7/15/20, Peregryn Winterwell<EMAIL_ADDRESS>wrote:

@amirsol81 Oh yes, I hear you on that! Thanks for the information about
Merriam-Webster, I'll do some digging on my own because I'm curious about
representation.
I'm using your merged file now, and I encourage everyone to grab that and
try it out, as it resembles what the August 1 release will be like. No doubt
questions and corrections will come up, but that's why this project is here.
Thanks for offering your experience and for your hard work, I hope you stick
around!
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/thunderdrop/IBMTTSDictionaries/issues/1#issuecomment-658430898

Can you submit your files as a PR or @thunderdrop merge them into the mainline repo? There's still room to change, a release is a reference to a specific commit so we can make multiple before calling it a release. There's just a lot of comments in this thread :). But glad we're having this discussion! and yes, I agree with your point of view regarding popularity, though I have a question on that front. The phrase "ad infinitem." It somehow got the latter part turned into infin item, but I'm not sure how widespread that is. And yes, Louisville should go in there the way that Jaybird recommended.

Can you submit your files as a PR or @thunderdrop merge them into the mainline repo? There's still room to change, a release is a reference to a specific commit so we can make multiple before calling it a release. There's just a lot of comments in this thread :). But glad we're having this discussion! and yes, I agree with your point of view regarding popularity, though I have a question on that front. The phrase "ad infinitem." It somehow got the latter part turned into infin item, but I'm not sure how widespread that is. I'm not saying we go with the probable Latin pronounciation where the e because ehh rather than schwa, I'm just voting here to leave it alone, the way eloquence already says infinitem. And yes, Louisville should go in there the way that Jaybird recommended.

May I know how I can submit my files as a PR? I'm clueless here as I haven't done it at all! 😀
As for ad infinitum, my .1nY.0fxm change is suggested virtually by all US English dictionaries -- AHD 5/FOxford/MW. In fact, not a single audio file from these dictionaries pronounces ad infinitum the way Eloquence does it. Moreover, both Alex and the relatively new WaveNet-based Siri female voice pronounce it that way -- I mean similar to my change. As for its popularity, I'm not sure because it's not a phrase whch one might encounter frequently. I'd say we keep my change but this is just my vote.
Finally, should I keep my altered pronunciation for Louisville?

@ultrasound1372 Oh I got your point re PR = pull request! 😀😊 I'll do that.

@ultrasound1372 I can't create a pull request. The Create Pull Request button is unavailable, meaning I can't select it no matter what I did/compared. So I had to create an issue:

@amirsol81 I have a few questions about rationale of some actions I've noticed in this merge. Firstly, I noticed that you had redone the stress on absolute, and all varriants. I think there's at least some where the stress would go on the u, for example absolutely. Also this breaks a sentence saying something like this statement is absolute, in that case I've always seen the stress go on the u. Furthermore, I noticed you included etc, but did not include misc. This is kind of nitpicky so I'll just ask if you meant to do that. Your file does not include the corrections for the names Rhyannan, Kirsten, Giana, or the compound asshat, that I've seen so far. Care to weigh in on these?

@ultrasound1372 Quite interestingly, an Eloquence user brought this to my attention. He told me that virtually all American English dictionaries, like Oxford American and Merriam-Webster, pronounce "absolute" and "absolutely" with the stress placed on the first syllable. Had I not checked it myself, I wouldn't have believed it. So based on this and Windows One Core's same pronunciations I was asked to alter both. I myself have qualms about them and will happily revert them to the original if requested.
As for etc, I'm surprised that it's there especially in Root. I'm not sure when I added it over the past 15 years -- maybe it was a consequence of not having access to Main.dic and Abbr.dic. But now that Eloquence for NVDA can take care of it with its Abbreviation feature in the Synthesizer dialog, I just removed it from Root. By the same token, I think the addition of misc isn't necessary as the same rule covers it. Any thoughts? For me both etc and misc are pronounced properly now.
Finally, I do see "asshat" in Root.dic -- maybe the pronunciation is what you deem incorrect -- is this the case? I'm dead sure I also added Rhyannan, Kirsten and Giana but am not sure why they aren't there. Of course, quite occasionally it happens to me that what I add via EloqTalk.exe isn't saved, but since the merge required the addition of a very number of words over the course of a few days, I didn't manage to check these. And may I ask you to kindly send the corrected phonetic forms for these 3 words? I'll correct and send them today along with some new additions.
Thanks.

@ultrasound1372 I just added Rhyannan, Kirsten and Giana based on the project's Root file. But as I said, asshat was already fixed.

@ultrasound1372 After taking an unusually closer look at the whole "absolute" story, , I decided not to mess around with such a contentious issue. Furthermore, AHD 5 supports the old Eloquence pronunciations. So I removed all "absolute" variants other than "absolutive" and "absolutistic" -- both being clear mispronunciations.

I agree that absolutive and absolutistic should have the stress there.  Perhaps it's just an invalid sequence, I'll check something. I myself won't be using the abbreviations feature as it's synths just trying to be more clever than they are, which is why etc and misc were in root. They should probably go in main if we want them outside of abbr.

OK so, what are your changes being made in? ENUroot.dic and ENUmain.dic? Because I still don't see these there.

Note: liblouis is not pronounced like that! It is named after Louis Braille, resulting in Lib Louis.

Note: liblouis is not pronounced like that! It is named after Louis Braille, resulting in Lib Louis.

Honestly I hadn't noticed that association. I'll be fixing it. Thanks.

OK so, what are your changes being made in? ENUroot.dic and ENUmain.dic? Because I still don't see these there.

Well, today I was planning to publish those two files. But it's proving quite cumbersome! I did everything, made the commit, and tried to create the pull request. Everything apparently went well but at the end it displayed a "file conflict" message, saying ENURoot.dic has a conflict.
I'll give it a try tomorrow but if it proves to be such a hassle, guess I'd be better off emailing them to one of the members here along with a list of my added/altered words so that they can make them available.

Why are you creating a pull request? You can push directly. Yes, files have been updated since then. So in your local repo, git pull, let it do the merge, it should merge fine. Then push.

The month of July has ended. Also, due to general versioning practices, version numbers will not prefix a 0 on single digit months.

@ultrasound1372 Thanks for your stupendous efforts. Just a suggestion: wouldn't it be a good idea to include the Read Me file in the ZIP archive?


Tutorial clarification - why does it work without the mapped entity's methods?

I inherited a project with a OneToMany relation that didn't have any methods for setting the 'many' holder (e.g. 'reportedBugs' in User.php of the tutorial).
Out of curiosity, I cloned the tutorial and removed the assignedToBug() and addReportedBug() calls from src/Bug.php, and everything still appears to work.  If I grab a User repository and ask it to get assignedBugs, they're there, as are any new ones I create with create_bug.php.
In fact, the property seems to keep up-to-date even if I create a new bug and list a User's bugs in the same php process!
Apparently doctrine is doing some magic behind the scenes that's new since the tutorial was written?

@bitwombat In the Bug mapping, we define @ManyToOne(targetEntity="User", inversedBy="assignedBugs").
The assignedToBug() and addReportedBug() have nothing to do with the fact that (if you grab a user from the repository) the list of reportedBugs gets filled.

The assignedToBug() and addReportedBug() have nothing to do with the fact that (if you grab a user from the repository) the list of reportedBugs gets filled.

Then what are those methods for then?  Are they for keeping Users, which have already been grabbed from the repository, in-sync?  If so, then it's plausible that this app I inherited, which doesn't have the equivalent functionality, might not need it.

Thanks @coudenysj .  I get (from the docs) that only changes to the many side cause an update to the db.  Since my experiment described above works, I can only assume that the syncing functions (e.g. assignedToBug() and addReportedBug()) are there to keep the objects in sync when in memory changes occur.  Is that correct?


[S2T] paddlecloud/paddlespeech:develop-gpu-cuda11.2-cudnn8-latest 最简单的例子也没法跑

For support and discussions, please use our Discourse forums.
If you've found a bug then please create an issue with the following information:
Describe the bug
最简单的例子也没法跑
To Reproduce
paddlespeech asr --lang zh --input zh.wav
Expected behavior
A clear and concise description of what you expected to happen.
 paddlespeech asr --lang zh --input zh.wav
grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py:121: DeprecationWarning: pkg_resources is deprecated as an API
  warnings.warn("pkg_resources is deprecated as an API", DeprecationWarning)
/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('mpl_toolkits')`.
Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
  declare_namespace(pkg)
/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('google')`.
Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
  declare_namespace(pkg)
/usr/local/lib/python3.7/dist-packages/librosa/core/constantq.py:1059: DeprecationWarning: `np.complex` is a deprecated alias for the builtin `complex`. To silence this warning, use `complex` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.complex128` here.
Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  dtype=np.complex,
/usr/local/lib/python3.7/dist-packages/paddle/fluid/framework.py:1104: DeprecationWarning: `np.bool` is a deprecated alias for the builtin `bool`. To silence this warning, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here.
Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  elif dtype == np.bool:
W0613 08:46:25.913857 30879 gpu_context.cc:278] Please NOTE: device: 0, GPU Compute Capability: 8.0, Driver API Version: 12.2, Runtime API Version: 11.2
W0613 08:46:25.918004 30879 gpu_context.cc:306] device: 0, cuDNN Version: 8.1.
TypeError: declarative() got an unexpected keyword argument 'property'

Environment (please complete the following information):

开发者你好，感谢关注 PaddleSpeech 开源项目，抱歉给你带来了不好的开发体验，目前开源项目维护人力有限，建议参考：https://github.com/PaddlePaddle/PaddleSpeech/issues/2512


Alexa discovery works after using Hue app

I've been looking at all the issues for a couple of weeks and finally got round to trying some stuff in code without much success. However I stumbled across this by accident... I have a Philips Hue app on my iPhone. This is not connected to a cloud account.

Discovery from Alexa always fails, regardless of if Alexa's just been reset or not.
Discovery using the Philips app to find a new hub results in the app stating there's a new hub it can't manage as the app only supports v2 hubs
After running the discovery in the Philips app, my device shows up in the Alexa app

I haven't sniffed any traffic as I don't have the time but I can only assume that the Philips doing some kind of announcement or multicast which Alexa's catching and deciding there's a new legit device available.

My hue app crashes when i try to connect to esp


Fix count warning php 7.2

See this issue

Awesome, thanks for the fix!
Could you also add PHP 7.2 (and 7.3, if you want) to our Travis testing matrix?

Thanks! We may want to give columnHeaders an empty array as default value, but this is a good fix for now.

Tagged as 1.0.1.

Thanks! We may want to give columnHeaders an empty array as default value, but this is a good fix for now.

Yeah that's what I did first, but I thought that in case of an empty row, the condition would be true and that's probably not what's expected.


HostEndpoint objects remain after calico node is deleted

It looks like when a kubernetes worker node is deleted (when etcd datastore is being used), the calico node data, WorkloadEndpoints, etc are all deleted as well for that node.  However the HostEndpoint object(s) associated with that node are not deleted.  Is this a known issue, and any chance it could be changed to also delete the HostEndpoints associated with that node?  It seems like the HostEndpoint objects that were associated with that node are now useless and should be deleted.
Expected Behavior
All objects, including HostEndpoints, that are associated with a calico node object should be deleted when the calico node object is deleted
Current Behavior
HostEndpoint objects associated with a given Node object are not deleted when that Node object is deleted (at least not in etcd datastore mode)
Possible Solution
Delete them
Steps to Reproduce (for bugs)

Create a k8s cluster with calico in etcd datastore mode with a few worker nodes, and HostEndpoints for each of the nodes (doesn't matter if there are policies applied or not)
Delete one of the k8s cluster worker nodes
Notice that all the data associated with those workers go away, except for the HostEndpoints

Context
Our IKS cluster workers automatically get a public and private HostEndpoint (to protect the public and private network interfaces on the worker).  We have customers that use a worker autoscaler to regularly create and delete many nodes a day.  The nodes and most associated objects (WEPs, etc) get cleaned up by calico-kube-controllers, but the HostEndpoint objects remain, and there is no good way to clean up the ones that aren't in use.
Your Environment

Calico version: Various, we've seen this behavior in 3.13 and below (haven't tried it on newer versions yet)
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes (version doesn't matter)
Operating System and version: Ubuntu
Link to your project (optional):

I'll try to dig into whether this is intentional or not, but feels like we should be deleting these.

@caseydavenport Any update on this?

Certainly looks like it was just omitted in this code, where we delete all the other per-node resources on deletion: https://github.com/projectcalico/libcalico-go/blob/34d8399da1480a4f47a32d2bb205cc59d7319ec1/lib/clientv3/node.go#L174-L221

Sorry for the delay on this guy, but working on a fix here: https://github.com/projectcalico/libcalico-go/pull/1355


Possible fix for macOS windows opening with the wrong viewport size

This appears to fix the issue with macOS windows opening with the wrong viewport size/scale by ensuring that the open gl viewport is set in the coordinate space of the underlying window which may have a different scale factor. I do not know if this works on any other platforms, but it seems like it should.

@BigZaphod thanks, I'll review it. Maybe some users don't want the Window scaled on HighDPI...

The FLAG_WINDOW_HIGHDPI doesn't seem to have any effect for me on macOS when I set it. I'm not sure what the intent of the flag is, really, but setting it or not seems to result in no change that I'm noticing. (I must point out that this is literally the first time I've even used Raylib, so I'm not really in a great position to suggest a change like this and feel a bit nervous about even sending it - but it does seem to fix the problem on my end for the examples, anyway!)

@BigZaphod It breaks the rendering on Windows platforms, just pushed a commit with a fix.