This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/11837] GB18030-2005 is not supported!
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sources dot redhat dot com
- Date: Sat, 16 Jul 2011 00:44:42 +0000
- Subject: [Bug localedata/11837] GB18030-2005 is not supported!
- Auto-submitted: auto-generated
- References: <bug-11837-716@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11837
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #8 from Rich Felker <bugdal at aerifal dot cx> 2011-07-16 00:44:36 UTC ---
GB18030 is defined to map not just every Unicode *character*, but every
*Unicode Scalar Value*. That means every number in the ranges 0x0000-0xD7FF and
0xE000-0x10FFFF is mapped. This property is what makes it a true UTF and not
merely a legacy DBCS.
Mr. Drepper, if you claim GB18030 should not successfully map unassigned
codepoints, what about the converters between UTF-8, UTF-16, and UTF-32? Should
they also reject unassigned codepoints? Despite being horribly ugly and having
all the harmful properties of legacy DBCS, GB18030 is a UTF and should be
treated the same as other UTFs.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.