Win32 is a special case ("UCS-2LE"), *BSD & QNX were another special case
("UCS2"), and the default - presumably Linux? - was "UCS-2BE"/"UCS-2LE"

Curious about that. Do *BSD & QNX use libiconv? Is it libiconv which is
really the special case?

Peanut uses libiconv and has spelling issues, so it's not a case of a
deficient iconv implementation, and yet libiconv seems to have problems
with "UCS-2BE"/"UCS-2LE" - and does not, according to the README, have a
"UCS2" option so why that works I am uncertain. "UCS-2-INTERNAL" is
however a valid option and seems to work...

I hope this patch doesn't break *BSD & QNX - please test!

o Use "UCS-2-INTERNAL" rather than "UCS-2BE", "UCS-2LE" or even "UCS2" when
  building against GNU libiconv.

CVS:----------------------------------------------------------------------
CVS: Enter Log.  Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS:    src/af/util/xp/ut_iconv.cpp
CVS:----------------------------------------------------------------------

Regards, Frank

Francis James Franklin
[EMAIL PROTECTED]

"No, she really likes me. She told me I look like Britney Spears, and why
would you say that to somebody you don't like?"
                                                           --- Elle Woods


Reply via email to