If you want the converted string in any of the formats other than UTF-8, UCS-2, UTF-16LE, or UTF-16BE, you have to do the conversion yourself. Lots of free conversion algorithms are available in the web which can be used for the conversion.
At 12:00am -0700 8/27/04, [EMAIL PROTECTED] wrote:
I have seen following #defines in Palm Locale.h // Unicode character encodings #define charEncodingUCS2 CHAR_ENCODING_VALUE(9) #define charEncodingUTF8 CHAR_ENCODING_VALUE(6) #define charEncodingUTF7 CHAR_ENCODING_VALUE(24) #define charEncodingUTF16 CHAR_ENCODING_VALUE(75) #define charEncodingUTF16BE CHAR_ENCODING_VALUE(76) #define charEncodingUTF16LE CHAR_ENCODING_VALUE(77) #define charEncodingUTF32 CHAR_ENCODING_VALUE(84) #define charEncodingUTF32BE CHAR_ENCODING_VALUE(85) #define charEncodingUTF32LE CHAR_ENCODING_VALUE(86) #define charEncodingUTF7_IMAP CHAR_ENCODING_VALUE(87) #define charEncodingUCS4 CHAR_ENCODING_VALUE(88)
Does this means All theabove types arenot be supported by TxtConvertEncoding????
Correct - the charEncodingXXX values defined in PalmLocale.h are a larger set than the encodings supported by the device.
However Y Rekha's response to your first email was slightly in error. Starting with Palm OS 5.3, the following Unicode encodings are supported:
charEncodingUCS2
charEncodingUTF8
UTF16
UTF16LE
UTF16BE
UTF32
UTF32BE
UTF32LE
charEncodingUCS4Also note that the additional encodings (beyond Unicode) supported by a device depend both on the OS version and the device's character encoding. For example, a Japanese device using the PalmShiftJIS character encoding will support conversion to/from Shift-JIS, but that won't be the case for an English device using the PalmLatin character encoding.
-- Ken -- Ken Krugler TransPac Software, Inc. <http://www.transpac.com> +1 530-470-9200
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
