From: Keld Simonsen <keld@keldix.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: Mikhail Gribanov <mikhail.gribanov@gmail.com>,
libc-alpha@sourceware.org, bug-glibc-locales@gnu.org
Subject: Re: Incorrect days of the week in ru_UA locale
Date: Tue, 01 Oct 2019 20:54:00 -0000 [thread overview]
Message-ID: <20191001205442.GB12438@www5.open-std.org> (raw)
In-Reply-To: <1380310075.857991.1569959113276@poczta.nazwa.pl>
On Tue, Oct 01, 2019 at 09:45:13PM +0200, Rafal Luzynski wrote:
> 28.09.2019 19:37 Keld Simonsen <keld@keldix.com> wrote:
> >
> > I think we should use lowercase that is what we do with manuyothe european
> > locales
> > and it is the culturally correct form
> >
> > keld
>
> Thank you for your feedback, Keld. Unfortunately, as a native speaker
> of one of those languages I must say that this is more complex.
> Indeed, names of the weeks and months are usually lowercase but
> when they appear in the beginning of a sentence they are uppercase.
> I am afraid that a name of a weekday more often appears in the beginning
> of the sentence than in the middle. To the extent that some locales
> prefer the weekday and/or month names to start with the uppercase.
I am also a native speaker of one of those languages, Danish, and moreover I was the initial contributer of about 60 of the locales incl ru_RU,
that Urich Drepper picked up for glibc. I am also the editor of ISO 14652 and ISO 30112 that provided extensions
beyond Posix i18n functionality, and I provide guidance for their use. My advice is that this bad policy to have wrongly
capitalized names here.
> What we actually need is a new format modifier to control the first
> letter being uppercase/lowercase. Currently we have only "^" to convert
> whole substring (e.g., a weekday name) to uppercase, and "#" to swap
> the upper/lowercase. It was discussed in the past, there is a bug
> report and a proposal to ensure that "^#" works as a converter to
> lowercase but this is not enough because I would like to see one more
> format modifier to convert to titlecase (that is: the first letter
> being uppercase). I would be happy to work on that problem but
> it is a separate case and would need more discussion.
I agree with you, and it has been my plan as editor of ISO 30112 to add functionality along the lines that you suggest,
without having a firm propoal.
> Back about the main problem, I would like to post a patch which would
> be the best explanation what I mean in this particular case.
What would it say?
keld
next prev parent reply other threads:[~2019-10-01 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 15:25 Mikhail Gribanov
2019-09-27 15:44 ` Florian Weimer
2019-09-27 22:49 ` Rafal Luzynski
2019-09-28 17:25 ` Keld Simonsen
2019-10-01 19:45 ` Rafal Luzynski
2019-10-01 20:54 ` Keld Simonsen [this message]
2019-10-02 7:33 ` Mikhail Gribanov
2019-10-02 7:36 ` Mikhail Gribanov
2019-10-02 22:14 ` Rafal Luzynski
2019-10-03 6:24 ` Mikhail Gribanov
2019-10-05 8:04 ` Maciej W. Rozycki
2019-10-05 19:58 ` Rafal Luzynski
2019-10-05 8:56 ` Keld Simonsen
2019-10-05 20:16 ` Rafal Luzynski
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=20191001205442.GB12438@www5.open-std.org \
--to=keld@keldix.com \
--cc=bug-glibc-locales@gnu.org \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
--cc=mikhail.gribanov@gmail.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).