Re: iconv output utf-8 -> utf-16, which one is wrong?

[Edmund GRIMLEY EVANS]

> > You could argue that putting a BOM is the application's duty, not
> > iconv's business, but that would be painful for all applications which
> > try to use iconv. And unlabelled data (e.g. files on a filesystem)
> > shouldn't use UTF-16 or its variants in the first place, that what
> > UTF-8 is for.
> > 
> 
> Well, the issue is that iconv() is also used for, say, text strings
> embedded in data.  However, it sounds like the solution is simply to
> request UTF-16BE instead.

So, UTF-16 gives you bigendian with BOM, UTF-16BE gives you big-endian
without BOM and UTF-16LE gives you little-endian without BOM.

How do I ask for the machine's native ordering with or without BOM?

Edmund
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/