public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "myllynen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16975] New: Revisit yesstr/nostr LC_MESSAGES capitalization in all locales
Date: Thu, 22 May 2014 08:23:00 -0000 [thread overview]
Message-ID: <bug-16975-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16975
Bug ID: 16975
Summary: Revisit yesstr/nostr LC_MESSAGES capitalization in all
locales
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: myllynen at redhat dot com
CC: libc-locales at sourceware dot org
>From https://sourceware.org/glibc/wiki/Locales:
"In yesstr and nostr the beginning should reflect whether the beginning of the
word is capitalized or in lowercase. This is in line with other specifications
in glibc locales, where e.g. day names and month names reflect the use of lower
and upper case as prescribed in dictionaries, which records the canonical form
of the word or phrase. This is also in accordance with use in POSIX and ISO TR
14652, and general guidelines for definitions in ISO/IEC."
For the background discussion, see the yesstr/nostr messages found at
https://sourceware.org/ml/libc-locales/2013-q2/.
But instead of fixing locales one by one, most/all locales should be revisited
at the same to make this uniform policy change.
This bug is to track this change.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-05-22 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 8:23 myllynen at redhat dot com [this message]
2014-06-12 19:12 ` [Bug localedata/16975] " fweimer at redhat dot com
2014-07-01 9:29 ` myllynen at redhat dot com
2014-07-01 9:30 ` myllynen 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-16975-131@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).