Salesforce

Building a Magic xpa Language File (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Building a Magic xpa Language File (Magic xpa 3.x)

Magic xpa needs a translation file that includes the original string, that is the string as entered when developing the application, and the translated string. For each language, you need a separate translation file.

The translation file is a simple text file with the following format:

OriginalString1

TranslatedString1

OriginalString2

TranslatedString2

OriginalString3

TranslatedString3

Each text string must be on a separate line. A blank line must be left at the end of the file.

The translation file must be converted to a Magic xpa language file using the MLS_BLD.EXE utility (executed from a command prompt).

The syntax of the MLS_BLD command is:

MLS_BLD <source> <destination> <code page>

where:

  • source – the translation file specified above

  • destination – the Magic xpa language file (create by MLS_BLD)

  • code page – an optional code page to be used; if omitted, the default code page will be used

The MLS_BLD command line utility does not check for the existence of a destination file, and will always overwrite an existing file with the same name.

Related Topics

The Online and Rich Client Samples projects (program EV13 and REV13)

Reference
Attachment 
Attachment