public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/13951] Correct L10n of country-name dz_BT
Date: Sun, 23 Dec 2012 13:28:00 -0000	[thread overview]
Message-ID: <bug-13951-716-SViKoheusU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13951-716@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13951

--- Comment #4 from Chris Leonard <cjlhomeaddress at gmail dot com> 2012-12-23 13:27:03 UTC ---
After a thoughtful and welcome discussion on libc-alpha, 

thread start:
http://sourceware.org/ml/libc-alpha/2012-11/msg00439.html

a contact from the Dzongkha Development Commission was able to resolve some
uncertainties about the proper representation of the countryname "Bhutan" in
Dzongkha

http://sourceware.org/ml/libc-alpha/2012-12/msg00321.html

Per that e-mail, 

"The short (abbreviated) name of Bhutan is simply འབྲུག (U+0F60 U+0F56 U+0FB2
U+0F74 U+0F42) "

"as to the question of whether to put U+0F0B or U+0F0D on the end:

 - if you are concatenating the string with other Dzongkha (or Tibetan
words) you would probably need U+0F0B.
- if the string occurs at the end of a phrase or sentence you use U+0F0D
- if the string occurs alone you can either leave it as it is - or add U+0F0D"

Given it's appearance in the LC_ADDRESS field, the most common usage is
presumed to be in postal addressing, not in concatenation with other words.  

Therefore, the patch as originally submitted is in correct form (it includes
the U+0F0D character at the end).

Unless further discussion is indicated on whether or not an LC_ADDRESS
countryname can be presumed to be a stand-alone or terminal element, I would
respectfully request commit of the patch as submitted.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-12-23 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  4:54 [Bug localedata/13951] New: " cjlhomeaddress at gmail dot com
2012-04-06  4:54 ` [Bug localedata/13951] " cjlhomeaddress at gmail dot com
2012-04-06  4:55 ` cjlhomeaddress at gmail dot com
2012-04-06  7:15 ` cjlhomeaddress at gmail dot com
2012-06-27  5:25 ` cjlhomeaddress at gmail dot com
2012-11-20 21:04 ` cjlhomeaddress at gmail dot com
2012-11-20 23:57 ` cjlhomeaddress at gmail dot com
2012-12-23 13:28 ` cjlhomeaddress at gmail dot com [this message]
2012-12-23 19:02 ` cjlhomeaddress at gmail dot com
2012-12-27  9:02 ` cjlhomeaddress at gmail dot com
2013-01-03  9:05 ` aj at suse dot de
2014-06-25 12:10 ` fweimer 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-13951-716-SViKoheusU@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).