![background image](http://html1.mh-extra.com/html/omron/cx-supervisor/cx-supervisor_user-manual_744211231.webp)
Translating User Defined Text Manually
SECTION 15 Multilingual Features
230
If you need translations for the same text in different contexts, Show the
Object ID column and select the Add new object ID string button. Select the
application text for the new translation and the object context for this special
case. This is in the format PageName followed by a dot followed by
ObjectName for example MyPage.Push_1
Any text that includes a quote " character cannot be stored so is automatically
converted to single quote ' character. Translations must also include single
quote characters.
To enter a 'newline' in the edit field hold the <Ctrl> key and press the Return
key.
15-5
Translating User Defined Text Manually
1, 2, 3…
To get the user defined text translated and incorporated follow these steps:
1. Develop your application completely. It is easier (and more effective) to
perform these steps just once. However if further development is required,
repeat these steps and use a development tool like WinGrep, Visual
Sourcesafe or other version control software which should easily show the
changes that have been made.
2. Export the user defined text by selecting menu Project|Create User
Language File. This will create a file in the project directory called
"default.udt".
3. Copy this file for as many translations as are required. Name each copy
<language>.udt using exactly the same text (particularly the accents), as
appears in the Language Settings dialog. If the filename prefix is not
exactly the same the file will not be loaded. The format of these files is:
"development text","translated text",optional object ID
The object ID (e.g. "Text_1") is optional but can be supplied if specific text
requires different translations for different objects. For example "Run" in
English could be used as a verb on a button, and as static text for a run
number. In this case different translations can be supplied depending on
the object.
4. Get these files translated. An editor like Notepad can be used to enter the
translated text in the second column i.e. in-between the quotes after the
first comma.
5. Copy the translated files back to the application directory. The runtime
should now automatically use these files.
Note:
Titles of pages cannot be translated. If necessary the page title can be hidden
in the Page Properties dialog, and custom title using a static text object added
which does support automatic translation.
Note:
Any text that includes a quote " character cannot be stored so is automatically
converted to single quote ' character. Translations must also include single
quote characters.
Note:
Any newline characters will be converted to "\n" so that each translation
always appears on one line in the file. Translations should also include the "\n"
characters and never include carriage returns part way through the translation.
Summary of Contents for CX-Supervisor
Page 1: ...CX Supervisor Software Cat No W10E EN 01 User Manual Software Release 3 1...
Page 3: ...Copyright Notice 2...
Page 16: ...15...
Page 17: ...16...
Page 27: ...Tip of the Day SECTION 1 Graphics Editor 26...
Page 35: ...CX Supervisor Preferences SECTION 2 Pages 34...
Page 79: ...Responding to Events SECTION 5 ActiveX Objects 78...
Page 115: ...Printing the Graphics Library SECTION 7 Graphics Library 114...
Page 181: ...Data Logging SECTION 11 Data Logging 180...
Page 201: ...Examples SECTION 12 Databases 200...
Page 243: ...Performance Monitor SECTION 16 Application Analysis Performance Monitor 242...
Page 253: ...Using with Omron s CX Server OPC SECTION 17 Using CX Supervisor as an OPC Cli 252...
Page 259: ...Creating a CX Supervisor Client application SECTION 18 Connecting to a remote CX 258...
Page 263: ...Adding a Point Linked to a Parameter SECTION 19 Connecting to Omron Industrial 262...
Page 271: ...Data Logging SECTION 20 Best Practices 270...
Page 275: ...Configuring a Server PC running Windows NT or 2000 Appendix A Configuring a PC 274...
Page 277: ...Appendix B Frequently Asked Questions 276...
Page 296: ...Appendix B Frequently Asked Questions 295...
Page 297: ...Appendix B Frequently Asked Questions 296...
Page 298: ...Appendix B Frequently Asked Questions 297...
Page 299: ...Appendix B Frequently Asked Questions 298...
Page 333: ...Revision history 332...