From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/20862] mo_MD@cyrillic: new locale
Date: Sat, 26 Nov 2016 01:57:00 -0000 [thread overview]
Message-ID: <bug-20862-716-45LNus7Jk2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20862-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20862
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2016-11-26
CC| |carlos at redhat dot com
Ever confirmed|0 |1
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
Vlad,
Thank you very much for the locale contribution.
Please review our contribution checklist:
https://sourceware.org/glibc/wiki/Contribution%20checklist
Please note that you do _not_ need copyright assignment to contribute locales,
however the patch will have to be sent to libc-alpha@sourceware.org for
eventual review.
(a) Use of 'mo' versus 'ro' for locale langauge tag.
Please be aware that as of 2008 the 'mo' tag has been deprecated in favour of
using the 'ro' tag. Therefore for a new locale we should probably be using
'ro_MD@cyrillic' for the Moldovan language using Cyrillic script.
(b) LC_IDENTIFICATION category should always be "i18n:2012" since it must
specify a published standard of i18n.
(c) Is the mon_thousands_sep and thousands_sep intended to be a non-breaking
space instead of a period as is used in original Romanian?
(d) Please fill in more of the LC_ADDRESS entries as provided by other locales
e.g. lang_*.
(e) Please test installing and using your locale. Existing checks for invalid
LC_IDENTIFICATION categories should have rejected your locale IIRC. Please
confirm you have tested compiling and using your locale e.g.
https://sourceware.org/glibc/wiki/Locales#Testing_Locales
Thank you.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-11-26 1:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 21:13 [Bug localedata/20862] New: Please add the new mo_MD@cyrillic locale cybernenea11 at cyberdude dot com
2016-11-24 21:13 ` [Bug localedata/20862] " cybernenea11 at cyberdude dot com
2016-11-25 21:25 ` [Bug localedata/20862] mo_MD@cyrillic: new locale vapier at gentoo dot org
2016-11-26 1:57 ` carlos at redhat dot com [this message]
2016-11-26 1:58 ` carlos at redhat dot com
2016-11-29 11:09 ` cybernenea11 at cyberdude dot com
2016-11-29 11:09 ` cybernenea11 at cyberdude dot com
2017-01-04 7:01 ` cybernenea11 at yandex dot com
2017-10-21 8:14 ` maiku.fabian at gmail dot com
2024-01-18 9:15 ` maiku.fabian at gmail dot com
2024-01-18 9:31 ` maiku.fabian at gmail dot com
2024-01-18 9:36 ` 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-20862-716-45LNus7Jk2@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).