From: "bluebat at member dot fsf.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/16905] New: New collation for hanzi
Date: Mon, 05 May 2014 08:45:00 -0000 [thread overview]
Message-ID: <bug-16905-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16905
Bug ID: 16905
Summary: New collation for hanzi
Product: glibc
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: bluebat at member dot fsf.org
CC: libc-locales at sourceware dot org
Created attachment 7586
--> https://sourceware.org/bugzilla/attachment.cgi?id=7586&action=edit
hanzi collation by stroke
Please find attached the collation for hanzi(chinese characters) to be
considered for inclusion in glibc.
The order is based on the stroke data from http://www.cns11643.gov.tw/
There is already iso14651_t1_pinyin in glibc, so I just named this file as
iso14651_t1_stroke which may not be a proper name.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-05-05 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 8:45 bluebat at member dot fsf.org [this message]
2014-05-20 6:09 ` [Bug localedata/16905] " bluebat at member dot fsf.org
2014-06-12 20:04 ` fweimer at redhat dot com
2014-10-13 9:18 ` bluebat at member dot fsf.org
2014-11-07 5:18 ` bluebat at member dot fsf.org
2014-11-07 11:30 ` bluebat at member dot fsf.org
2015-08-21 9:53 ` bluebat at member dot fsf.org
2016-02-19 10:49 ` [Bug localedata/16905] hanzi: new collation vapier at gentoo dot org
2016-08-02 21:05 ` bluebat at member dot fsf.org
2017-07-19 16:12 ` maiku.fabian at gmail dot com
2017-07-20 2:22 ` bluebat at member dot fsf.org
2017-08-10 11:50 ` bluebat at member dot fsf.org
2017-08-10 12:07 ` cvs-commit at gcc dot gnu.org
2017-08-10 13:09 ` bluebat at member dot fsf.org
2017-08-10 13:13 ` maiku.fabian at gmail dot com
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-16905-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).