Hi Chris: After a couple of days of using the word "cap" to indicate capital letters I am ready to jump out of my skin with the delay waiting for the word cap to complete and not hearing the letter I type but only the word "cap" unless I pause after typing every letter that I capitalize for some time. I know you are likely not a professional programmer but that "cap" indicator is a real pain trying to type computer code at any speed.. I do programming and in the world of pros we use camel casing for allot of words like: StockMetrixTableClass and dbDDLClass. Typing the capitals requires stopping and listening to the word cap until it is done then I can type the next letter with confidence but in programming there are hundereds if not thousands of caps that need to be typed and often in sequence making the word cap real hassle versus a pitch change and slowing things down. I want to evaluate some synths to see which one would work decently with my computer and WindowEyes. How do I evaluate them to see how changing voicing, pitch, speed and other WE settings impact reading of selected material as I type, reading of caps as I type, latency and lag times as well as just listening to a sample voice reading something. I want to know which synths work properly with WindowEyes and which ones have weaknesses or problems for the type of high speed work I do before throwing money at one of them. Note typeing the letters U S A below read nothing but cap cap cap unless I wait until the word cap was completey spoken for each letter. Rick USA
_______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
