From: "hanataka.shinya at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22669] New: New localedate for ja_JP （suppoted UTF-8 and JIS X 4061 collation)
Date: Thu, 04 Jan 2018 03:08:00 -0000 [thread overview]
Message-ID: <bug-22669-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22669
Bug ID: 22669
Summary: New localedate for ja_JP （suppoted UTF-8 and JIS X
4061 collation)
Product: glibc
Version: 2.26
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: hanataka.shinya at gmail dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
Created attachment 10710
--> https://sourceware.org/bugzilla/attachment.cgi?id=10710&action=edit
four files for ja_JP locale
I have update ja_JP loclaedata. It is suppoted unicode characters and JIS X
4061 collation rules.
In more detail the following changes are included.
- support unicode character in LC_CTYPE and LC_COLLATE
- support JIS X 4061 with some extesion in LC_COLLATE
- slightly update in LC_MONETARY and LC_NUMERIC to fonfirm int standard
- update in LC_ADDRESS to fit the standard order of Japanese Address.
Four file is attached.
ja_JP: new localefile for Japan
ja_JP@compatible: old localedata for backward compatibility
coll_jisx4061_ex: JIS X 4061 collation rule which called from ja_JP
coll_jisx0208: comaptibility collation rule which call from ja_JP@compatible
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-01-04 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 3:08 hanataka.shinya at gmail dot com [this message]
2018-02-09 11:00 ` [Bug localedata/22669] " maiku.fabian at gmail dot com
2019-09-10 13:52 ` carlos at redhat 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-22669-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).