Multiple Language Support

If you must support more than two non-English languages, you must use the LANG=en_US.UTF-8 setting. In addition, your database (Oracle or DB2) and application/collaboration server must be configured for UTF-8. If your data is in multiple languages, your browser also must have the appropriate language support.

Note: To support filenames with special characters, manually change the LANG setting to en_US.UTF-8 in mxEnv.sh and mxEnvCAS.sh.

See About Localizing Live Collaboration.

Note: An error may occur in the HOME page when the format of a Windows server is set to use Japanese, for example.

Generally speaking, the recommended configuration for servers is LANG=en_US.UTF-8 and MX_CHARSET=UTF8. This allows the server to handle multiple languages for different users, thereby avoiding date formatting issues.

But if you must configure the server in the Japanese language, this type of issue can be avoided by using:

MX_NORMAL_DATETIME_FORMAT="moy/dom/yr4 h24:min:sec"

instead of:

MX_NORMAL_DATETIME_FORMAT="moy/dom/yr4 h12:min:sec mer"

and setting the following values in the emxSystem.properties file:

eServiceSuites.eMatrixDateFormat = MM/dd/yyyy HH:mm:ss
eServiceSuites.eMatrixInputDateFormat = MM/dd/yyyy HH:mm:ss

These are the recommended settings for an app server/TC/JVM that handles DBCS:

LANG=en_US.UTF-8
export LANG
NLS_LANG=_.AL32UTF8
export NLS_LANG
MX_CHARSET=UTF8
export MX_CHARSET

Note: LANG=C should not be used.