About Localizing ENOVIA Live Collaboration

This topic describes how each layer of the stack is translated. UTF-8 configuration for the application servers is mostly done by default with a few steps required to be done manually. See UTF-8 Settings for details.

Language support is outlined in "Language Support".

The table below shows the files used to localize each part of ENOVIA Live Collaboration:

Items to be localized ENOVIA Studio Modeling Platform ENOVIA Matrix Web Navigator Other ENOVIA products
User Interface menus, dialogs, tips matrix.txt, matrix.vr Java class files that get compiled with ENOVIA Matrix Web Navigator (no changes in field) emxAPPNAMEStringResource_LANG.properties

emxComponentsStringResource_LANG.properties

Java class files that get compiled with applets (such as checkin applet, Gantt Chart applet, etc.) (no changes in field)
Schema objects Language Aliases Language Aliases emxFrameworkStringResource_LANG.properties
Lower level schema objects (policy states, attribute ranges) one language only (administration definition) one language only (administration definition) emxFrameworkStringResource_LANG.properties
Error messages from ENOVIA Live Collaboration Server matrix.txt, matrix.vr (file on the client) smatrix.txt, matrix.vr (file on the server) matrix.txt, matrix.vr (file on the server)
APPNAME is the name of the application; LANG is the 2-digit ISO code.

ENOVIA products default to English if the translated string cannot be found. This can occur for several reasons. The most obvious is when the Web browser is configured for a language that is not provided. Also, MQL keywords are not localizable, and so these are always shown in English. In some cases, most strings appear localized, with a few showing up in English. This occurs when text is added late in the software release cycle, and you can assume that they will be updated in a future release. However, in other cases, the English word is preferred by the ENOVIA translation reviewer, and so will remain untranslated. If this is the case, and you have another preference for the string, you can modify the provided file(s). The one exception to this is for ENOVIA Matrix Web Navigator. The localization is handled by Java files that must be compiled with the source code.

Note: The database and Application servers must be correctly configured to handle UTF-8 encoding.

Filenames

In a UTF-8 environment, strings are not processed in the kernel. The ENOVIA Live Collaboration Server just passes them to the database as received. However, one exception is for file checkin through the server using the workspace directory–standard checkin, not File Collaboration Server (FCS). ENOVIA Live Collaboration hashes file names on checkout in the workspace directory, but does not hash file names on checkin. So, an English server configured for UTF-8 treats a UTF-8 encoded file with double-byte characters in the name being checked in as consisting of extended ASCII characters and succeeds in creating a file in the workspace directory. But the database expects UTF-8 bytes and so produces an error on checkin. However, the sequence of bytes in the file name are the same on the native and English operating systems. Also, the file content is encoded correctly.

The workaround is to use FCS for all file checkins through a ENOVIA Live Collaboration Server.