public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19485] csb_PL: update month translations
Date: Sat, 23 Apr 2016 06:01:00 -0000	[thread overview]
Message-ID: <bug-19485-716-FYukHcVkAp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19485-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=19485

--- Comment #8 from Mike Frysinger <vapier at gentoo dot org> ---
please don't take this personal.  the problem we have with locales is that
people often make requests & post patches that are wrong.  either it's a
personal preference or they just don't realize what the actual standard
behavior is supposed to be.  which means we, who are not experts in these
langs, are left as the ill-prepared gatekeepers.  in the past, it meant that
changes rarely went in when we couldn't validate things.  now, we're trying to
automate by relying on projects that have more critical mass to vet things. 
unfortunately for csb, it's not in many of these projects, so we have to fall
back to the old method: trying to locate references to validate a user's
request.

the references i've found say "strumiannik", not "strëmiannik".  which is why
i've been pushing to try and locate somethings that suggest "strëmiannik" is
actually correct.  for example, a Polish gov't site that lists the month names
and uses the latter form instead of the former form.

if i wanted to tell you to "just go away", i would have closed the bug long ago
and told you to pound sand ;).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2016-04-23  6:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  8:37 [Bug localedata/19485] New: Update for csb_PL (Kashubian) locale data ostrowski.michal at gmail dot com
2016-01-18  8:38 ` [Bug localedata/19485] " ostrowski.michal at gmail dot com
2016-01-18 13:18 ` [Bug localedata/19485] csb_PL: update month translations vapier at gentoo dot org
2016-04-22  3:08 ` vapier at gentoo dot org
2016-04-22 13:17 ` ostrowski.michal at gmail dot com
2016-04-22 22:02 ` vapier at gentoo dot org
2016-04-22 22:03 ` ostrowski.michal at gmail dot com
2016-04-23  4:12 ` vapier at gentoo dot org
2016-04-23  5:27 ` ostrowski.michal at gmail dot com
2016-04-23  6:01 ` vapier at gentoo dot org [this message]
2016-04-23  6:28 ` ostrowski.michal at gmail dot com
2016-06-29 15:39 ` piotrdrag at gmail dot com
2017-10-30 12:07 ` cvs-commit at gcc dot gnu.org
2017-10-30 12:12 ` maiku.fabian at gmail dot com
2017-11-02 22:56 ` digitalfreak at lingonborough dot com
2017-11-03  9:19 ` digitalfreak at lingonborough dot com
2018-06-21 10:51 ` digitalfreak at lingonborough dot com
2018-06-25 10:24 ` [Bug localedata/19485] csb_PL: Update month translations + add yesstr/nostr digitalfreak at lingonborough dot com
2018-06-25 10:46 ` cvs-commit at gcc dot gnu.org
2018-06-25 10:51 ` digitalfreak at lingonborough dot com
2018-08-01  6:01 ` cvs-commit at gcc dot gnu.org

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-19485-716-FYukHcVkAp@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).