Kbase P44382: TranMan II. Is it possible to use TranmanII to translate from Latin Locale Application to Asiatic Lo
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/12/2004 |
|
Status: Verified
GOAL:
TranMan II. Is it possible to use TranmanII to translate from Latin Locale Application to Asiatic Locale Application?
GOAL:
Is Tranman able to handle with the 2 Locales?
CAUSE:
Application developped in plain English should be translated to Chinese.
FIX:
Yes this is possible and this has been tested.
You should first consider a few things before starting to do the translations.
1. For the test we have choose Windows XP because this OS has been enhanced with more Linguistic Support and you are able to work with Different Input Locales at the same time.
2. In the Regional Setting of XP:
- Settings -> Control Panel
- Regional Options: -- CHINESE HONKHONG & Location in CHINA
- Languages: I have added the Chinese HonkHong Keyboard for the tests and selected Supplemental Languages Support. (You can continue with the default keyboard in way to swith to chinese only when needed).
-Advanced: In Select the language to match -> Chinese(HonkHong).
3. Reboot your XP box.
On the Translation Manager Side:
1. The Default locale for Tranman DB is by default UNDEFINED. No needs to change it.
2. Create your project in TranMan (New).
3. Extract the strings for translation from the application procedures.
4. Create your Kit.
5. In Virtual Translator, translate your strings to chinese (by switching to the additional Chinese Keyboard we have previously added), your chinese character strings will appear by typing them in the field for translation.
6. Return the Kits to TranMan.
7. Consolidate the Kits.
8. Compile the application selecting before the target language.
9. From TranMan you can run on the fly one or more translated procedures or you can use the comand line as follow to launch the application in the target language:
prowin32 DBname -p programname.w -lng chinese
Other considerations:
If you plan to work with different Client Locales against the same DB you should consider to work with an UTF-8 DB since this Codepage accepts most of the Locales of the world. In V9.x UTF-8 is not yet supported on the client, so you will have to start each client with their own locale.
If you do not plan to work with different input Locales from diferent clients, then you could keep the same input locales for the Db and the Clients.