Hi all, See emails below. I am just wondering if there is any simple way of managing Builtin.dic as part of the NVDA locale? Thanks, Ronan ---------- Forwarded message ---------- From: Ronan McGuirk <ronan.p.mcguirk@xxxxxxxxx> Date: Thu, 17 Jul 2014 21:28:03 +0100 Subject: Re: Optional splitting of words containing embedded capital letters into multiple words? To: nvda-devel@xxxxxxxxxxxxxxxxxxxxx Hello again, We have discovered a partial solution to this issue. Commenting out the second line in the builtin.dic file in the NVDA folder solves this problem. Would it be possible for builtin.dic to become a part of the NVDA locale? For instance, a tailered version of builtin.dic could be used for the Irish language in the locale\ga folder, that would be used instead of the regular builtin.dic. Or am I missing a simpler solution? Many thanks, Ronan On 25/06/2014, Ronan McGuirk <ronan.p.mcguirk@xxxxxxxxx> wrote: > Hello, > > I would like to re-visit a query that came up about 18 months ago. > > This relates to the Irish language (Gaeilge) but may be an issue in > other languages. > > There is a construction in Irish grammar where a capital letter can > occur within a word close to the start of the word for example > "mBaile" or "bhFear" > > These should be pronounced as single words. However, if I am correct, > NVDA seems to split camelCase words into multiple parts, assuming that > a new word begins at a capital letter. > > This issue is resolved in the Irish implementation in eSpeak, which > has rules for dealing with the situation. > For instance for the word mBaile, when eSpeak sees the single letter > word "m" followed by a word beginning with "b" it silences the m and > changes the pronunciation of the word beginning with b to take account > of the m. In effect, this is re-attaching the split words back to > intact words. > > Would it be possible for NVDA to make this splitting of camelCase > words an option? > > This would be of benefit for the development of other Irish language > synthesisers. (It may also be useful in other languages). > > If this is resolved already in NVDA, can you let me know how to approach > this? > > Many thanks, > Ronan >