Before I start, I am just getting to know the orca code in detail
myself so may not be able to point at exactly where changes should be
made. Reading what you say about how you might detect the language this should work on any unicode string. In this case could this be done only in the speech output stage? By this I mean Orca scripts produce speech output through the orca.speech module. Even if that isn't exactly where the changes would need to be made in the output process, you should be able to follow the path of the text to be output from there. You probably would also want to modify the Orca preferences offered to users so they could configure such a feature, but I am unsure where those changes would be. Now I will give a few warnings on what you suggest (these are based on thoughts rather than trying what you suggest). * If all output speech were to be tested for language, how will this impact on the responsiveness of orca? * Users may want to turn it off (possibly for performance reasons, I use English and more than 99% of the time I am reading English with orca). * Considering the possible amount of use, is there any particular applications where you would want such a feature? In my case about all of the text in other languages (the little of it I read) is from firefox. * If there are specific applications, are there better ways of detecting language? I think openoffice knows about the language of the text (don't know whether or how we get that information). * Might it be better as an application specific script? * To remove the need for automatic detection (which may not be accurate in all cases anyway) would having a shortcut key for a language selection menu be enough? I will be honest and say I am probably biased as my use of other languages is very low, but I am just cautious of this having a negative impact on a significant number of users if done wrongly. Michael Whapples On 02/08/2010 04:06 AM, anila susan wrote: Hi Michael, |