#588991 libc-bin: iconv doesn't document the meaning of ambiguous encoding names such as "UNICODE"

Package:
libc-bin
Source:
glibc
Description:
GNU C Library: Binaries
Submitter:
Neil Mayhew
Date:
2010-07-14 10:00:06 UTC
Severity:
wishlist
#588991#5
Date:
2010-07-14 04:33:36 UTC
From:
To:
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.
#588991#10
Date:
2010-07-14 09:57:19 UTC
From:
To:
severity 588991 wishlist
tag 588991 + wontfix
thanks

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.