barrymavin
2014-05-22, 06:09
The following character encodings are supported.
Apple Roman
Big5
Big5-HKSCS
CP949
EUC-JP
EUC-KR
GB18030-0
IBM 850
IBM 866
IBM 874
ISO 2022-JP
ISO 8859-1 to 10
ISO 8859-13 to 16
Iscii-Bng, Dev, Gjr, Knd, Mlm, Ori, Pnj, Tlg, and Tml
JIS X 0201
JIS X 0208
KOI8-R
KOI8-U
MuleLao-1
ROMAN8
Shift-JIS
TIS-620
TSCII
UTF-8
UTF-16
UTF-16BE
UTF-16LE
UTF-32
UTF-32BE
UTF-32LE
Windows-1250 to 1258
WINSAMI2
The character encoding should be automatically picked up from your locale but if you want to develop for different locales you can specify:
--locale name_from_above_list
Note that you may omit the prefix e.g "8859-1" is the same as "ISO 8859-1" and "874" is the same as "IBM 874"
On the desktop shortcut that launches the App Builder or the App Center.
For non latin character sets in eastern europe you need to specify
--locale Windows-1250
Note that when a different locale is used you can specify locale specific characters in variable and field names also.
Lianja best practices strongly advise that you should use utf-8 rather than a windows specific codepage locale.
--utf8
Unicode/UTF-8 is the industry standard nowadays and any character from any language can be displayed.
UTF-8 is also more web/mobile friendly.
Apple Roman
Big5
Big5-HKSCS
CP949
EUC-JP
EUC-KR
GB18030-0
IBM 850
IBM 866
IBM 874
ISO 2022-JP
ISO 8859-1 to 10
ISO 8859-13 to 16
Iscii-Bng, Dev, Gjr, Knd, Mlm, Ori, Pnj, Tlg, and Tml
JIS X 0201
JIS X 0208
KOI8-R
KOI8-U
MuleLao-1
ROMAN8
Shift-JIS
TIS-620
TSCII
UTF-8
UTF-16
UTF-16BE
UTF-16LE
UTF-32
UTF-32BE
UTF-32LE
Windows-1250 to 1258
WINSAMI2
The character encoding should be automatically picked up from your locale but if you want to develop for different locales you can specify:
--locale name_from_above_list
Note that you may omit the prefix e.g "8859-1" is the same as "ISO 8859-1" and "874" is the same as "IBM 874"
On the desktop shortcut that launches the App Builder or the App Center.
For non latin character sets in eastern europe you need to specify
--locale Windows-1250
Note that when a different locale is used you can specify locale specific characters in variable and field names also.
Lianja best practices strongly advise that you should use utf-8 rather than a windows specific codepage locale.
--utf8
Unicode/UTF-8 is the industry standard nowadays and any character from any language can be displayed.
UTF-8 is also more web/mobile friendly.