Kbase 16462: Using TranMan II to translate a character mode application.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/2/2000 |
|
Using TranMan II to translate a character mode application.
How to use TranMan II to translate a character mode (CHUI)
application:
1) Migrate the application to the most current version.
2) Since TranMan II only runs under MS-Windows(either Win/95
or 3.1), copy the source code and database schema to an
MS-Windows platform to do the translation. To do this, use the
Data Dictionary to dump the database schema into a .df file and
then transfer all the source files along with the .df file to an
MS-Windows machine. Once on the Windows machine, use the Data
Dictionary to rebuild the database using the transferred .df.
3) Using TranMan II, translate the application. One note, is
that when making the "resource files", select a "Display Type"
of "Character" instead of the default "Graphical". This gives the
display a "character mode" appearance when the "Visual Translator"
renders them for the Translator.
4) Once all the translations have been made, and all of the
various "kits" have been consolidated back into the Project
Database, use the Data Dictionary to dump the Project Database
into a .df file along with 13 .d files (all of the hidden tables
that start with "XL_"). Transfer these 14 files back to the
original machine with the original character mode application.
5) Back on the character mode platform, use the Data Dictionary
to rebuild the project Database from the .df and .d files that
were just transferred.
6) Make sure that the newly constructed Project Database (Step 5) is
connected with a logical name of "xlatedb" and that all of the
necessary application databases are connected. Compile the
application source code with the LANGUAGES parameter set to include
all of the desired languages.
7) Test the entire application making sure all of the translations
look right and fit on the display properly. Repeat steps 3 through 7
as neccessary.
NOTES:
- to identify a string during compilation a relative path from TranMan
"Project Source Directory" is used as one of attributes. The path
and procedure name is stored in XL_instance.proc_name. Same string
has to be used with COMPILE statement. For example:
if XL_instance.proc_name is "source/p/myproc.p" compile statement
has to be: COMPILE source/p/myproc.p SAVE LANGUAGES ... .
If COMPILE ./source/p/myproc.p SAVE LANGUAGES ... is used instead,
procedure is compiled (r-code is bigger than without LANGUAGES
option), but only original strings are displayed.
- the same applies if Application Compiler is used
- XL_instance.proc_name is NOT case-sensitive and both "/" and "\" can
be used
Progress Software Technical Support Note # 16462