public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bone.burma at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/13605] Please add the new Shan (shn) locale
Date: Tue, 29 Jul 2014 08:00:00 -0000 [thread overview]
Message-ID: <bug-13605-131-YZhJPVCD6M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13605-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13605
Bone Pyae Sone <bone.burma at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bone.burma at gmail dot com
--- Comment #3 from Bone Pyae Sone <bone.burma at gmail dot com> ---
Hi!
I attached the Shan locale file since 2012 and it seem still no effect to
include the Shan Language in any other open-source OS. I developed the locale
for the Shan Community around the world to use the system in their language so
that they can help to develop the education, development and living standards
of the Shan from the rural areas.
I urge whoever taking care of this to consider it for the sake of these people.
With Best Regards,
Bone Pyae Sone.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2014-07-29 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 15:57 [Bug localedata/13605] New: " kokoye2007 at gmail dot com
2012-02-17 3:24 ` [Bug localedata/13605] " mistresssilvara at hotmail dot com
2012-07-09 6:03 ` bone.burma at gmail dot com
2012-07-15 9:58 ` mistresssilvara at hotmail dot com
2014-06-27 11:10 ` fweimer at redhat dot com
2014-07-29 8:00 ` bone.burma at gmail dot com [this message]
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-13605-131-YZhJPVCD6M@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).