Kbase P7028: How to use Translation Manager to translate Character mode applications on a different platform.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/9/2008 |
|
Status: Verified
GOAL:
How to use Translation Manager to translate Character mode applications on a different platform.
FACT(s) (Environment):
Translation Manager 2.0
All Supported Operating Systems
FIX:
1.) On any platform where the source code exists compile the source with the STRING-XREF option.
2.) Move the xref output file to the Windows system where the Translation Manager resides.
3.) Run Translation Manager and go through the steps to create a project EXCEPT you skip the Extract step on the Data tab. During the Load step, use the .xrf file that was created on the other platform.
4.) Translate strings into other language(s).
Assuming you have a file with the following code:
/* d:/9/ade/trans/initial.p */
DEFINE VARIABLE l-capital AS CHARACTER INITIAL "D.C." NO-UNDO.
DEFINE VARIABLE l-country AS CHARACTER INITIAL "U.S." NO-UNDO.
MESSAGE l-capital l-country VIEW-AS ALERT-BOX.
where:
- TranMan is started from dir d:/9/ade/
- Project name is p-initial
- "English" and "Spanish" are defined
The strings are translated to "D.F." and "Mexico" when translating from English to Spanish.
The user should verify that the initial value are indeed translated by using menu Build->Compile and Build->Run. Running in both English and Spanish.
5.) Dump the .df and .d files from the TranMan DB.
For example: p-initial.df
xl_cust.d
xl_glsry.d etc.
6.) Move these files to the target system using FTP or some other method.
7.) Create an empty DB on the target system (make sure that the DB name is the same as the original TranMan DB), load the table definitions and data into this new DB.
prodb empty p-initial
8.) Using the Procedure Editor or Application Compiler on the target system, connect to both the application DB and the new TranMan DB.
Connect to p-initial with logical name of "xlatedb", make sure that all files are placed in a directory structure identical to the one in the PC (where TranMan was used).
For instance, if you will be starting the PROGRESS session in the dir /users/devp/user1
then the initial.p should be placed in /users/devp/user1/trans
such that the HOME dir for the PROGRESS session will look at trans/initial.p
THIS IS KEY TO MAKING THIS WORK CORRECTLY.
9.) Compile the source code with the languages option. Multiple languages can be specified at this time (only languages in the TranMan DB should be specified).
COMPILE VALUE("trans/initial.p") LANGUAGES("English,Spanish") SAVE.
10.) Run the compiled code with the languages startup parameter. Only one language may be chosen at this time.
For example, -lng "french"
You can test by either (in procedure editor)
CURRENT-LANGUAGE = "Spanish".
RUN VALUE("trans/initial.p").
or (at the command line)
pro -p trans/initial.p -lng "Spanish"
Steps 5 - 7 are only necessary when compiling translated code on a non DOS or Windows system.