From: Mike Frysinger <vapier@gentoo.org>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: libc-alpha@sourceware.org, libc-locales@sourceware.org
Subject: Re: use of Yy+0/Nn-1/etc... in LC_MESSAGES yesexpr/noexpr
Date: Mon, 18 Apr 2016 17:45:00 -0000 [thread overview]
Message-ID: <20160418174526.GU5369@vapier.lan> (raw)
In-Reply-To: <2068255263.341464.927dd0c6-0cc1-4eda-8a2d-7a80cd0843a6.open-xchange@poczta.nazwa.pl>
[-- Attachment #1: Type: text/plain, Size: 2046 bytes --]
On 18 Apr 2016 11:10, Rafal Luzynski wrote:
> 18.04.2016 04:40 Mike Frysinger wrote:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=15262
> > do we have policy/guidance on the use of english chars in the yes/no
> > regexes ? of the 202 locales that define yesexpr/noexpr, 195 of them
> > include [Yy]/[Nn], most of which aren't english.
> >
> > my take: at the risk of being called anglocentric, we should add
> > [Yy] & [Nn] to all locales
>
> Sounds reasonable to me. From my own experience and from my contacts
> with other developers from neighboring countries it seems to me that
> hardcore computer users (software engineers, admins, scientists, long
> time users) are used to English and sometimes even prefer English over
> their own native languages and sometimes may involuntary press Y/N
> instead of their native version even if the software is localized.
> My point is that adding [Yy] and [Nn] can make some people happy and
> will not hurt anybody.
>
> Note: Make sure that [Yy] and [Nn] are not already used for the opposite
> meaning (that [Yy] does not mean "no" or [Nn] does not mean "yes")
> because in that case this change would be harmful.
a very good point. there's 5 languages where this comes up:
yo.xml: <yesstr>Bẹẹni :N</yesstr>
sw.xml: <yesstr>Ndiyo:N</yesstr>
guz.xml: <nostr>Yaya:Y</nostr>
az.xml: <nostr>yox:y</nostr>
uz.xml: <nostr>yo‘q:y</nostr>
at least yo_NG is broken on our side.
> - no, please don't drop [Oo] (Oui) from en_CA unless preserving [Oo]
> causes some technical issues;
i split this out into the other reply by Keld
> - yes, please use [ДдDdYy] and if possible for both sr_RS and sr_RS@latin;
> I guess that some Serbian users may use different keyboard layouts and
> switch between them, it would be easier for them if the software could
> read their intention correctly even if they forget to switch their
> keyboard layout to Latin.
script variants are much easier to handle as we have that data :).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-18 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 2:41 Mike Frysinger
2016-04-18 9:10 ` Rafal Luzynski
2016-04-18 17:45 ` Mike Frysinger [this message]
2016-04-18 11:22 ` Keld Simonsen
2016-04-18 17:44 ` Mike Frysinger
2016-04-18 21:21 ` Rafal Luzynski
2016-04-18 21:53 ` Mike Frysinger
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=20160418174526.GU5369@vapier.lan \
--to=vapier@gentoo.org \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@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).