The following table summarizes what might be translated for built applications, the translation methods used, and the file names involved.
Translation Of: | Method | File Name |
---|---|---|
System messages | MSGTRANS | NGEN28/MLSLIBRARY |
Valid values of Maint | MSGTRANS | NGEN28/MLSLIBRARY |
System responses | MSGTRANS | NGEN28/MLSLIBRARY |
Administration (colon) command teach information | Text Editor | NGEN28/1/LTEACH |
Screen Display items (for built applications) | FTU or Painter | system/LINCFORM |
Teach screens (for built applications) | FTU or Editor | system/LINCFORM |
Captions | FTU or MME | system/ MULTILANG |
Alphanumeric attributes | FTU or MME | system/ MULTILANG |
Report Display items | Painter | report |
Maint
All valid values for the Maint built-in attribute that might be translated are in the MLSLIBRARY file. In particular, translations of the values Add, CHG, DEL, PUR, and INQ are accessible within logic as the built-in attributes Glb.Add, Glb.Chg, Glb.Del, Glb.Pur, and Glb.Inq, respectively.
Report Display items
Report Display items are hard-coded in your built Reports. Different Report names must be used to obtain different language versions.
References
Captions are descriptive attributes allocated to attributes for use in user messages. Refer to the Agile Business Suite Developer User Guide for more information.
Refer to the Agile Business Suite Developer User Guide for more information on Segment attributes.
Report Output Control system, which are accessible from applications, are also translatable. Refer to Translating ROC for more information.
Utilities, which can be run against applications, are also translatable. Refer to Translating Utilities for more information.