They support. But what happens is that the presence of the BOM tells
the compiler that I am using my file in UTF-8, but not only that. It
also tells the compiler that I want it to automatically convert my
strings from UTF-8 to whatever the operating system expects.
Therefore FPC correctly handled my UTF-8 strings and tryed to convert
then to the codepage of my operating system (probably latin ISO), and
my simbols have no ISO correspondent, so they would be removed.
By not using BOM I am not telling the compiler anything, so it won't
do any automatic conversions.
I could also use BOM, but still set the codepage compiler directive in
my code to get the behavior I want, which is no automatic encoding.
It may not technically be a bug since they don't claim to support a
BOM
that's not what was claimed.
--
Felipe Monteiro de Carvalho
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
