From: "kokoye2007 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/25139] Please add the new mnw_MM locale
Date: Tue, 05 Nov 2019 13:58:00 -0000 [thread overview]
Message-ID: <bug-25139-716-2VNm6Smf7T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25139-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25139
--- Comment #6 from kokoye2007 <kokoye2007 at gmail dot com> ---
[error] LC_ADDRESS: terminology language code `mnw' not defined
[error] LC_ADDRESS: language abbreviation `mnw' not defined
[error] LC_ADDRESS: language abbreviation `mnw' not defined
we just need to fix
lang_ab - two-letter ISO 639 code if available, empty if not (when only
three-letter code is available)
lang_term - three-letter ISO 639-2/T (Terminology) code
lang_lib - three-letter ISO 639-2/B (Bibliographic) code
```
lang_ab "mnw"
lang_term "mnw"
lang_lib "mnw"
```
@@ -11,7 +11,7 @@
LC_IDENTIFICATION
title "Mon language locale for Myanmar"
-source "Mon Localization Team
https:////facebook.com//groups//monlocalization"
+source "Mon Localization Team
https:////facebook.com//groups//monlocalization//"
address "Mawlamyine, Mon State, Myanmar"
contact "Talachan Mon"
email "talachanmon@gmail.com"
@@ -212,17 +212,17 @@
LC_NUMERIC
decimal_point "."
thousands_sep ","
-grouping 3
+grouping "3;3"
END LC_NUMERIC
LC_MONETARY
currency_symbol "K"
int_curr_symbol "MMK "
-positive_sign ""
-negative_sign "-"
mon_decimal_point "."
mon_thousands_sep ","
-mon_grouping 3
+mon_grouping "3;3"
+positive_sign ""
+negative_sign "-"
frac_digits 2
int_frac_digits 2
p_cs_precedes 0
@@ -271,13 +271,10 @@
country_name "<U1017><U105F><U102C>"
country_post "Myanmar"
country_ab2 "MM"
-country_ab3 "MMR"
country_num 104
country_car "MYA"
-country_isbn 99971
% မန်
lang_name "<U1019><U1014><U103A>"
-lang_ab "mnw"
lang_term "mnw"
lang_lib "mnw"
END LC_ADDRESS
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-11-05 13:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25139-716@http.sourceware.org/bugzilla/>
2019-10-28 13:50 ` gunnarhj at ubuntu dot com
2019-11-04 19:07 ` kokoye2007 at gmail dot com
2019-11-04 19:41 ` kokoye2007 at gmail dot com
2019-11-04 19:42 ` kokoye2007 at gmail dot com
2019-11-04 19:43 ` kokoye2007 at gmail dot com
2019-11-04 19:45 ` kokoye2007 at gmail dot com
2019-11-05 9:24 ` maiku.fabian at gmail dot com
2019-11-05 10:38 ` maiku.fabian at gmail dot com
2019-11-05 10:40 ` maiku.fabian at gmail dot com
2019-11-05 11:23 ` maiku.fabian at gmail dot com
2019-11-05 13:58 ` kokoye2007 at gmail dot com [this message]
2019-11-05 14:01 ` kokoye2007 at gmail dot com
2019-11-05 17:44 ` kokoye2007 at gmail dot com
2019-11-05 18:12 ` kokoye2007 at gmail dot com
2019-11-05 18:13 ` kokoye2007 at gmail dot com
2019-11-06 6:29 ` maiku.fabian at gmail dot com
2019-11-06 7:16 ` cvs-commit at gcc dot gnu.org
2019-11-06 7:16 ` cvs-commit at gcc dot gnu.org
2019-11-06 7:16 ` cvs-commit at gcc dot gnu.org
2019-11-06 7:17 ` maiku.fabian at gmail dot com
2019-11-12 2:11 ` maiku.fabian at gmail dot com
2020-01-10 16:00 ` 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-25139-716-2VNm6Smf7T@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).