From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/20952] yuw_PG: new locale
Date: Mon, 23 Oct 2017 16:46:00 -0000 [thread overview]
Message-ID: <bug-20952-716-1JRLIyJvwo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20952-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20952
--- Comment #1 from Mike FABIAN <maiku.fabian at gmail dot com> ---
Your locale contains:
LC_CTYPE
copy "i18n"
translit_start
include "translit_combining";""
% LATIN CAPITAL LETTER O WITH DIAERESIS.
<U00D6> "<U004F><U0308>"
% LATIN SMALL LETTER O WITH DIAERESIS.
<U00F6> "<U006F><U0308>"
translit_end
END LC_CTYPE
The included “translit_combining” already has:
% LATIN CAPITAL LETTER O WITH DIAERESIS
<U00D6> <U004F>
% LATIN SMALL LETTER O WITH DIAERESIS
<U00F6> <U006F>
I think your extra rules don’t add anything new, do they?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-10-23 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 23:19 [Bug localedata/20952] New: Please add the new yuw_PG locale nungon.localization at gmail dot com
2016-12-08 23:25 ` [Bug localedata/20952] yuw_PG: new locale vapier at gentoo dot org
2017-10-21 8:13 ` maiku.fabian at gmail dot com
2017-10-23 16:30 ` maiku.fabian at gmail dot com
2017-10-23 16:34 ` maiku.fabian at gmail dot com
2017-10-23 16:46 ` maiku.fabian at gmail dot com [this message]
2017-10-23 16:58 ` maiku.fabian at gmail dot com
2017-10-23 17:01 ` maiku.fabian at gmail dot com
2017-10-23 17:17 ` maiku.fabian at gmail dot com
2017-10-23 17:27 ` maiku.fabian at gmail dot com
2017-10-25 12:05 ` cvs-commit at gcc dot gnu.org
2017-10-26 6:10 ` maiku.fabian at gmail dot com
2017-11-11 14:24 ` digitalfreak at lingonborough 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-20952-716-1JRLIyJvwo@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).