[coLinux-devel] Re: [PATCH] Fix "clever" text editors that decide to add a BOM to the config file

[Martin K. <ka...@po...>]

>  > Also, take a look here:
>  > http://www.cl.cam.ac.uk/~mgk25/unicode.html#ucsutf
>  >
>  > scroll down to the part that reads:
>  > It has also been suggested to use the UTF-8 encoded BOM (0xEF 0xBB 0xBF)
>  > as a signature to mark the beginning of a UT   F-8file.Thispractice
>  > should definitely not be used on POSIX systems for several reasons etc

Well, you have to read it on the Windows side, too :-) I mean, if you 
have the CoLinux for Windows.
And it's as already mentioned a problem of reader to get the content.

> The patch is intended to fix those "brain dead" editors that add a BOM
> to an UTF-8 encoded file, not to encode one ourselfs.
> The XML library we use is a very simple one, and chokes on this.
Brain dead editors just ignore the fact, that the xml document written 
on Big-Endiand system has another sense as on Low-Endian. So, if your 
Notepad on WinXP just ignore this fact, you're using the M$ Ignorant 
Editor (note, that notepad can now UTF8).

Regards,
Martin