Hi list,
As it turned out, UltraEdit was the culprit. It had an "Auto detect
UTF-8 files" setting turned on by default, which apparently in UE means
"Convert to Unicode if it's XML".
Eric Blasenheim provided me with the correct answer with regard to the
extended ascii characters.
When outputting an XML file in MapBasic, one should remember using
Charset "WindowsLatin1" when opening the file.
And the output (8 bit) characters using WindowsLatin1 correspond to an
XML encoding named "windows-1252", not "utf-8" (or any other).
I'm sure there are similar matching charset/encoding pairs wrt.
WindowsLatin2 etc., but I personally don't know which these are (yet).
--
Best regards / Med venlig hilsen
Lars Nielsen
GisPro
-------- Original Message --------
I just got somewhat of a surprise, and wanted to hear whether anyone on
the list has encountered the same issue.
It seems that a MapBasic app, even when compiled with MB 4.1, is now
capable of writing a Unicode formatted file.
The trigger seems to be outputting an XML header tag line (<?xml ... ?>).
I'm not sure whether it's MIPro (using 7.8) or Windows 2000 that
intervenes, since I'm positive this behaviour hasn't always been present.
Unfortunately it gets the extended ascii characters wrong, and
specifying charsets throws an error, so I'm kinda stuck for now :-(
--
Best regards / Med venlig hilsen
Lars Nielsen
GisPro
_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l
