Thanks! That clarifies a ton of stuff right there including my assumption that the checkboxes offered by the startup options at installation is as fine-grained as you can go.
-----Original Message----- From: Tom Kingston [mailto:[email protected]] Sent: Thursday, December 08, 2011 4:44 PM To: [email protected] Subject: Re: is it a legal action to edit WE's set files directly to gain finer control of punctuation customization? Here's how I manage punctuation at the global level. Under the screen node, punctuation, I set everything except space to global, dictionary only. I set space to off because I generally don't want to hear it. For the few programs I do want to hear it I change it for the particular program set file and set its scope to program. Otherwise all punctuation that is spoken will be defined in the default character dictionary; char.chr. For program specific changes I create a dictionary for that program, associate it with a set file for the program, make the changes to that dictionary, then change the punctuation scope to program. This uses the trickle down effect wherein if there's a program specific dictionary it will be referenced first, then the default char.chr dictionary will be referenced. But if the substitution is found in the program specific dictionary the same entry will be ignored in the default dictionary. Hth, Tom On 12/8/2011 1:51 PM, Stephen Clower wrote: > Hello Katherine, > > It is not illegal to edit the XML content of the Window-Eyes set > files, but we don't officially support doing so. Remember that if you > inadvertently break something, you can reset the Window-Eyes defaults > via the Factory Settings option in the File menu. > > Regards, > Steve > > > > > On 12/8/2011 1:39 PM, Katherine Moss wrote: >> Hello all, >> I'm just curious whether it is a good idea to edit set files directly >> in order to get fine customization of punctuation. I'm asking because >> when you have miscellaneous punctuation marks checked during the >> startup wizard, words like don't, doesn't, and I'm are not pronounced >> correctly due to WE reading the apostrophes. This is driving me up >> the wall and I'm trying to take a bit of control of it without trying >> to replace the words in the dictionary and having to struggle to find >> the right mock word to replace them to ensure correct pronunciation. >> Thanks for any input. >> >> Katherine Moss, >> Administrator of the AccessCop Network, previously Raeder24.org. >> Visit us on the web at http://raeder24.org<http://raeder24.org/> >> >> >
