the uniEncode of stringToEncode uniEncode(stringToEncode[,language])
uniEncode("AB") -- returns "A",null,"B",null (on Intel)
uniEncode("AB") -- returns null,"A",null,"B" (on PPC)
uniEncode(inputText,"Japanese") -- converts Shift-JIS to Unicode
Use the uniEncode function to convert
Parameters:
The stringToEncode is any string, or expression that evaluates to a string.
The language is one of the following:
* ANSI (synonym for "English")
* Arabic
* Bulgarian
* Chinese
* English
* Greek
* Hebrew
* Japanese (Shift-JIS)
* Korean
* Polish
* Roman
* Russian (Cyrillic)
* Thai
* Turkish
* SimpleChinese (Simplified Chinese)
* Ukrainian
* Unicode (UTF-16)
* UTF8
* w (synonym for "Unicode")
Value:
The uniEncode function returns a Unicode string.
If you don't specify a language, the string has each character of stringToEncode either followed or led (depending on platform) by a null character.
If a language is specified, the uniEncode function returns the Unicode equivalent of the stringToEncode, assuming the appropriate single-byte encoding for the specified language.
Comments:
The uniEncode function is the inverse of the uniDecode function and inserts null bytes for Unicode compatibility. In other words, it turns
Note: You can use the UTF8 encoding only with the uniDecode and uniEncodefunctions. You cannot set an object'stextFontproperty to use UTF-8. To display Unicode text in an object, use either "Unicode" or a language name as the second item of the object'stextFont.
Important! The format produced by the uniEncodefunction is processor-dependent. On "big-endian" processors, where the first byte is least significant (such as Intel and Alpha processors), the uniEncodefunction adds the nullbyte after each character. On "little-endian" processors, where the last byte is least significant (such as PowerPC processors), the uniEncodefunction adds the nullbyte before each character.
Changes to Revolution:
The ability to encode text in Polish was added in version 2.1.1.
The ability to handle double-byte characters on "little-endian" processors was added in version 2.0. In previous versions, the uniEncode function always added the null byte after the character, regardless of platform.
The ability to convert language-specific encodings into Unicode text was added in version 2.0. In previous versions, the uniEncode function simply added a null byte.
The solution is to encode and decode the content:
#tData contains your data read in from file put uniDecode(uniEncode(tData, "UTF8")) into tData
(All credit to Dave Cragg and Devin Assay for this tip)
put url ("binfile:/path/to/file/myUniText.ut8") into tRawTxt
set the unicodeText of fld "display" to uniEncode(tRawTxt,"UTF8")