Bug#588991: libc-bin: iconv doesn't document the meaning of ambiguous encoding names such as "UNICODE"
severity 588991 wishlist
tag 588991 + wontfix
thanks
On Tue, Jul 13, 2010 at 10:33:36PM -0600, Neil Mayhew wrote:
> Package: libc-bin
> Version: 2.11.2-2
> Severity: normal
> Tags: upstream
>
>
> Encoding names like "UNICODE" and "UCS-2" are ambiguous because the byte order
> isn't specified. It could be whatever is native for the platform, or it could
> be a canonical, host-independent order such as big-endian. This should be
> clarified somewhere.
>
This is not ambiguous, the byte order is either little endian ("UCS2-LE",
"UNICODELITTLE"), big endian ("UCS2-BE", "UNICODEBIG"), or native
("UCS2", "UNICODE").
All of these formats are listed in iconv -l.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: