From: "ldv at altlinux dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/11945] Month names in Russian Localization should be in lowercase
Date: Sat, 03 Nov 2012 17:16:00 -0000 [thread overview]
Message-ID: <bug-11945-716-4GsmYR6ddk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11945-716@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11945
Dmitry V. Levin <ldv at altlinux dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ldv at altlinux dot org
Resolution|FIXED |
--- Comment #8 from Dmitry V. Levin <ldv at altlinux dot org> 2012-11-03 16:18:56 UTC ---
Well, I have to comment on this finally.
First of all, the patch that was actually applied
(http://git.altlinux.org/gears/g/..git?p=glibc.git;a=commitdiff;h=glibc-2.13-145-gf498392)
does something very different from its description (Lowercase month names).
Besides the change of abbreviated month names to lowercase (which is probably
OK), it also slipped in a mix of other changes:
- change of abbreviated day names from fixed three-letter form to fixed
two-letter form (actually fixes
http://sourceware.org/bugzilla/show_bug.cgi?id=10873 which provides a good set
of references);
- unjustified addition of trailing dots to abbreviated day names (it's plain
wrong);
- unjustified addition of trailing dots to abbreviated month names (it's also
plain wrong);
- unjustified change of abbreviated month names from nominative to genitive
(it's also wrong and it actually reverts the fix made for
http://sourceware.org/bugzilla/show_bug.cgi?id=525);
- unjustified change of abbreviated month names from fixed three-letter form to
variable length form (just a nonsense).
Second, the procedure of describing changes, getting an approval from the
locale maintainer and providing good references (as described in
http://sourceware.org/glibc/wiki/Contribution%20checklist#Qualification_.28Locales.29)
was totally scrapped.
What I suggest in the way of recovery is to revert all these unjustified
changes. The only changes that can remain are:
- change of abbreviated month names to lowercase (a fix for this bug report);
- change of abbreviated day names to two-letter form (a fix for
http://sourceware.org/bugzilla/show_bug.cgi?id=10873).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-11-03 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11945-716@http.sourceware.org/bugzilla/>
2011-05-10 5:02 ` drepper.fsp at gmail dot com
2012-08-28 0:29 ` ldv at altlinux dot org
2012-08-28 0:29 ` dmitry at agafonov dot pp.ru
2012-08-28 22:28 ` ldv at altlinux dot org
2012-11-03 17:16 ` ldv at altlinux dot org [this message]
2012-11-05 16:41 ` ldv at altlinux dot org
2012-11-05 16:42 ` ldv at altlinux dot org
2014-05-28 19:53 ` schwab at sourceware dot org
2014-06-14 11:17 ` fweimer at redhat dot com
2010-08-25 12:58 [Bug localedata/11945] New: " martin dot pitt at ubuntu dot com
2010-08-25 12:59 ` [Bug localedata/11945] " martin dot pitt at ubuntu dot com
2010-08-25 13:02 ` martin dot pitt at ubuntu dot com
2010-09-05 17:26 ` mistresssilvara at hotmail 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-11945-716-4GsmYR6ddk@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sources.redhat.com \
/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).