### Creating control programs and translation files for a non-English system To have the WebCTRL® interface display a control program’s user-defined text (such as microblock names and property text) in a non-English language, you must: Create the control program using key terms instead of the text. Create translation files of key terms and their language-specific equivalents. In the WebCTRL® interface, the key term is replaced with its equivalent in the translation file for the current operator language. If a WebCTRL® Properties page or Logic page shows ??key term??, the key term is missing from the translation file. NOTE To edit existing control programs or translation files, see Editing translation files or control programs for a non-English system.
Click for details below To enter a key term in the EIKONŽ application Translation files To create and implement a translation file
#### To enter a key term in the EIKONŽ application In the EIKON® Property Editor, type`@` before each key term. NOTES Type only the key term in the EIKON® application. Expressions such as $present_value$ are put in the translation file as part of the translated text. See EXAMPLES in "Translation files" below. Key terms can contain only alphanumeric characters and underscores (no spaces) and cannot start with a number.
#### Translation files Translation files are used to translate key terms in control programs. A translation file contains key terms and their language-specific equivalents. For a non-English system, you must create an English translation file and a non-English translation file* for each of the following: Each control program Key terms used in multiple control programs EXAMPLES
Translation files | Key term=Language-specific equivalent
English | This_value=This value is $present_value$ Zone_temp=Zone temperature
Spanish | This_value=Este valor es $present_value$ Zone_temp=Temperatura de zona
*If the WebCTRL® interface will display multiple non-English languages, create a translation file for each language.
2. #### To create and implement a translation file Create your translation file in a text editor, such as Microsoft® Word, that supports the character encoding you need. Type one key term and language equivalent per line, left justified, starting in column 1. Do not put spaces on either side of the equal sign. Save the file using the appropriate file name and location in the table below.
   If key terms are used in... | the file name is... | File location
   A single control program | <any_name>_xx.native* | Any location
   Multiple control programs | equipment_xx.native* | WebCTRL\webroot\ <system_name>\resources
* xx = the language extension code. See "Extension codes and encoding" below. If you are using: the English character set, save the file as Text only. a non-English character set, save the file as Encoded text . (See your application’s help for information on saving files as encoded text.) When prompted for the language and encoding, see “Extension codes and encoding” below. Open the control program in the EIKON® application, then select Control Program > Bundled Resources. Click , locate and select the translation file(s) for this control program, then click Open. NOTES Do not add equipment_xx.native files that you created for multiple control programs. You can use Ctrl+click or Shift+click to select multiple files. Save the control program. The translation files are embedded in the control program; the original files are no longer necessary. Extension codes and encoding
Language | Extension codes | Encoding*
Brazillian Portuguese English Canadian French French German Italian Japanese Korean Russian Spanish Swedish Simplified Chinese Traditional Chinese Thai Vietnamese | pt_BR en fr fr_FR de it ja ko ru es sv zh zh_TW th vi | ISO-8859-1 ISO-8859-1 ISO-8859-1 ISO-8859-1 ISO-8859-1 ISO-8859-1 EUC-JP EUC-KR KOI8_R ISO-8859-1 ISO-8859-1 GB2312 Big5 TIS620 Cp1258
* Encoding is used when you create the translation file.