I would prefer that you choose the Window-Eyes language instead of the PC
Language. For example, I run an german Win7 at home with all Applications,
including Window-Eyes, in English. Just checking the OS Language would bring up
the app in german and not in English. This would be my preferred XML setting
<languageorder>WE,OS,en-us</languageorder>
Ralf Kefferpuetz
GCS Technical Operations Manager
Phone: +49 (0) 6196-4728-555
Mobile: +49 (0) 171-5582096
[cid:[email protected]]
From: David [mailto:[email protected]]
Sent: Tuesday, June 21, 2011 1:50 PM
To: [email protected]
Subject: Re: question for International Scriptors about WETranslator App
Default Language
To me, the user-choice seems the best. He would still have the chance of
choosing English, if that is his preference. For the app to choose a backup
language of its standard, will only cause frustration; I am afraid.
----- Original Message -----
From: RicksPlace<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Sent: Tuesday, June 21, 2011 1:36 PM
Subject: question for International Scriptors about WETranslator App Default
Language
Hi:
Right now I pickup the language from the culture settings on your computer and
Translate all the WETranslator app's User Interface into the language of your
Culture as the WETranslator MasterLanguage. Since there might not be Microsoft
Support for some Cultures I am deciding whether to use English as a backup
language or to pop up a list of valid Microsoft Translator languages for you to
pick from to use as the WETranslator MasterLanguage.
This language is for the WETranslator controls and User messages itself. The
App already supports picking any of the Microsoft Supported languages when
adding languages to a WE XML file.
My thoughts are that picking a language might be better. For example, if a
language is not supported you can pick from many languages like Spanish,
English, French and a host of other languages. That way you do not have to
speak English to use the WETranslator Application. By the way, most languages
are supported already and Microsoft is adding new ones all the time so this
might not even be a problem. But, it is a situation I can see cropping up as an
outside problem so dealing with it up front will be allot easier than after the
application is deployed.
Let me know which method you prefer.
Rick USA
