public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19575] New: Status of GB18030 tables
Date: Sat, 06 Feb 2016 00:38:00 -0000	[thread overview]
Message-ID: <bug-19575-716@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=19575

            Bug ID: 19575
           Summary: Status of GB18030 tables
           Product: glibc
           Version: 2.24
            Status: NEW
          Severity: normal
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: libc-locales at sourceware dot org
  Target Milestone: ---
             Flags: security-

In this commit:

commit 60cc4a18e6a2c865e250609a3021fa4ff2b57650
Author: Andreas Schwab <schwab@linux-m68k.org>
Date:   Mon Feb 6 13:30:45 2012 +0100

    Complete GB18030 charmap

Andreas updated the localedata/charmaps/GB18030 with additional mappings.  The
provenance of those is unclear.  They do not agree with the mapping table here:

http://source.icu-project.org/repos/icu/data/trunk/charset/data/xml/gb-18030-2000.xml

The difference is related to this choice in the glibc charmap

% <UE78D>     /xa6/xd9         <Private Use>
% <UE78E>     /xa6/xda         <Private Use>
% <UE78F>     /xa6/xdb         <Private Use>
% <UE790>     /xa6/xdc         <Private Use>
% <UE791>     /xa6/xdd         <Private Use>
% <UE792>     /xa6/xde         <Private Use>
% <UE793>     /xa6/xdf         <Private Use>
% <UE794>     /xa6/xec         <Private Use>
% <UE795>     /xa6/xed         <Private Use>
% <UE796>     /xa6/xf3         <Private Use>

versus:

<UFE10>     /xa6/xd9         PRESENTATION FORM FOR VERTICAL COMMA
<UFE11>     /xa6/xdb         PRESENTATION FORM FOR VERTICAL IDEOGRAPHIC COMMA
<UFE12>     /xa6/xda         PRESENTATION FORM FOR VERTICAL IDEOGRAPHIC FULL
STOP
<UFE13>     /xa6/xdc         PRESENTATION FORM FOR VERTICAL COLON
<UFE14>     /xa6/xdd         PRESENTATION FORM FOR VERTICAL SEMICOLON
<UFE15>     /xa6/xde         PRESENTATION FORM FOR VERTICAL EXCLAMATION MARK
<UFE16>     /xa6/xdf         PRESENTATION FORM FOR VERTICAL QUESTION MARK
<UFE17>     /xa6/xec         PRESENTATION FORM FOR VERTICAL LEFT WHITE
LENTICULAR BRACKET
<UFE18>     /xa6/xed         PRESENTATION FORM FOR VERTICAL RIGHT WHITE
LENTICULAR BRAKCET
<UFE19>     /xa6/xf3         PRESENTATION FORM FOR VERTICAL HORIZONTAL ELLIPSIS

It is not clear to me which one is correct.  Emacs chooses the <UE78D>
mappings, too.

Maybe the mapping changed over time, or there are conflicting practices.  Even
if it's a Private Use codepoint on the Unicode site, there should be a definite
mapping.

Further references:

http://www.unicode.org/mail-arch/unicode-ml/y2002-m07/0555.html
http://www.unicode.org/mail-arch/unicode-ml/y2003-m04/0277.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-02-06  0:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06  0:38 fweimer at redhat dot com [this message]
2016-02-08 13:34 ` [Bug localedata/19575] " schwab@linux-m68k.org
2016-02-08 13:35 ` fweimer at redhat dot com
2016-02-08 15:39 ` schwab@linux-m68k.org
2016-02-08 15:39 ` schwab@linux-m68k.org
2016-02-08 15:39 ` fweimer at redhat dot com
2016-02-08 15:39 ` carlos at redhat dot com
2016-02-08 21:12 ` carlos at redhat dot com
2016-02-08 21:12 ` carlos at redhat dot com
2016-02-08 21:51 ` schwab@linux-m68k.org
2016-02-08 21:51 ` schwab@linux-m68k.org
2016-02-09  8:39 ` schwab@linux-m68k.org
2016-02-24 23:55 ` cvs-commit at gcc dot gnu.org
2016-02-24 23:55 ` carlos at redhat dot com
2016-06-02 21:44 ` jsm28 at gcc dot gnu.org
2016-08-02  3:18 ` cvs-commit at gcc dot gnu.org
2023-05-22 19:00 ` bruno at clisp dot org
2023-05-22 19:05 ` bruno at clisp dot org
2023-05-22 19:07 ` bruno at clisp dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-19575-716@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).