LifeKeeper can operate in all system locales that are supported by Windows. However, locales that use multibyte character encodings (such as Japanese, Chinese, Korean, and other Eastern languages) may require that LifeKeeper be configured to use the correct encoding based on the system locale.
In order to do this correctly, a configuration file has been included in the core software which allows the user to specify the locale (including encoding) based on the system codepage, which is a numeric value that corresponds to the Windows locale for the system. The file is %LKROOT%\cygwin\usr\share\locale\locale.from.codepage. This text file can be customized if necessary – any lines that are not commented should be blank or should contain two values separated by a tab – the codepage numeric value, and the locale string to be used.
The locale.from.codepage file has already been populated with this value:
932 ja_JP.SJIS
To find a system’s codepage, you can run the powershell command:
[System.Text.Encoding]::Default.CodePage
Note that LifeKeeper will operate correctly in a multibyte locale without this file, as long as LifeKeeper does not need to access system resources whose name or value contains a multibyte character. For example, during creation of an IP Address, the name of the NIC is used. If the NIC is not named with a multibyte character, the IP Address creation will work regardless of whether this file has been configured for the system’s codepage.
Post your comment on this topic.