[fpc-pascal] Funny things about utf-8 strings on mac
florian at freepascal.org
Tue Jun 12 20:40:28 CEST 2007
Jonas Maebe schrieb:
> On 12 Jun 2007, at 11:41, Florian Klaempfl wrote:
>>> Looks somewhat illogical to me ... so I write a UTF-8 string and need
>>> a widestring managed? But I am not using widestrings ...
>> You're. String constants containing chars > 127 are obviously as
>> widestrings because when you give a code page in the source, you want
>> another encoding then the system's default i.e. the compiler needs to
>>> And then it will convert the string to iso??
>> ... or utf-8 ... depending on the setting of the system running the
> This seems too limited to me, as you may be communicating with an API
> that requires a different encoding than whatever is detected as default.
> A Mac OS X GUI app does not execute any .profile or so, so libiconv may
> very well default to some ISO encoding. That does not mean that people
> converting widestrings to ansistrings want to use this ISO encoding in
> all cases.
> There's utf8encode/decode, but it's quite annoying if you have to
> replace all widestring->ansistring assignments and parameter passing
> code with that call (especially since the type conversion from
> widestring to ansistring is supposed to do everything for you anyway).
You should simply leave away the codepage stuff then.
More information about the fpc-pascal