ENOVIA Applications

Each application relies on 3 base files, which are always in English:

• emxFrameworkStringResource.properties
• emxComponentsStringResource.properties
• emxAPPLICATION_NAMEStringResource.properties (For example, Engineering Central uses emxEngineeringCentralStringResource.properties)

When these files are translated, the translators work with the files in their native encoding, so that all special characters are displayed correctly. However, in order for the Java-based ENOVIA Live Collaboration Server to present the strings correctly, the files must be encoded in ASCII, and the filename must include the standard abbreviation for the language (as defined by ISO-639). This is true for all non-English languages, both double-byte and latin-based. For each translated file, ENOVIA provides both the native and the ASCII version, easily identified by the filename. For example, the files provided by ENOVIA Business Process Services for use in German are:

• emxTeamCentralStringResource_de.properties
• emxFrameworkStringResource_de.properties
• emxComponentsStringResource_de.properties
• emxMetricsStringResource_de.properties
• emxTeamCentralStringResource_deNative.properties
• emxFrameworkStringResource_deNative.properties
• emxComponentsStringResource_deNative.properties
• emxMetricsStringResource_deNative.properties

You only need the Native files if you want to make modifications to the out of the box translations. When you are done with the changes, you will need to run the native files through the native2ascii converter provided with the JDK. Refer to JDK documentation or Configuring Notifications and Messages under Configuring BPS Functions in the Studio Modeling - BPS Administration Guide for more information.

Note: ENOVIA products receive error messages and strings in the language known to the ENOVIA Live Collaboration Server. If no .vr file is available to the server, that language is English. Note that a server may be configured with no more than 1 .vr file.