Administering CA 2E Translator › Using CA 2E Translator Utilities › Additional Steps for Help Text Regeneration

Additional Steps for Help Text Regeneration

To incorporate the translated text into a Help Text document, the affected functions need to be regenerated. Do the following:

1. If translating at a remote site, create target environment libraries on the development machine for all remote environments using the same names.
2. Create a qtxtsrc or quimsrc file in the target environment library to hold the translated help text members.
3. If translating at a remote site, ship the translated model files in the target environment library (ytxtdta*) back to the same library on the development machine.
4. Set your help text generation model value to ygenhlp(*only), if required. This will cause only help text to be generated (not files and programs).
5. Include the Toolkit National Language libraries (y1syvxxxx y2syvxxx) in your library list above the product libraries to use the translated versions of the Help Text skeletons. These skeletons can be viewed in y2syvxxxx/ydftsrc or ydftuimsrc. See the section on Toolkit National Language libraries for a description of these libraries.
6. Regenerate help text to include the translated text. Change the ygenlib model value, or change the source and objects locations parameter to place all results in the target environment library, not the normal generation library.
7. Ship the resulting source (or objects if using UIM) back to the remote site, and reset model values, library list, and so on.

Note: Other text, such as condition names and field labels, are also included in generated text directly from within the model. Translation of this text should be performed on the generated source, using SEU or S/38 edttxt.