public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24652] szl_PL spelling correction
Date: Tue, 18 Jun 2019 00:23:00 -0000	[thread overview]
Message-ID: <bug-24652-716-uMyj6lZ6ps@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24652-716@http.sourceware.org/bugzilla/>

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

Rafal Luzynski <digitalfreak at lingonborough dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |digitalfreak@lingonborough.
                   |                            |com

--- Comment #1 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
Thank you for your contribution.

1. Can you please provide an authoritative (scientific etc.) source of your
data?  Usually our authoritative source is CLDR but unfortunately it does not
support Silesian.

1a. Can you consider adding Silesian to CLDR? 
http://cldr.unicode.org/index/bug-reports#New_Locales

2. Can you please provide the change as a git patch?  Make a local copy of
glibc repository, apply your changes, commit locally adding your comment, and
use "git format-patch" to generate the patch.  Then attach to this bug report.

3. Silesian is an inflected language so needs more changes:

    mon     "styczy<U0144>";/
            "luty";/
    ...

this should be probably:


    alt_mon "styczy<U0144>";/
            "luty";/
    ...
    mon     "stycz<U0144>a";/
            "lutygo";/
    ...

I can't speak Silesian so this may be wrong.  Also please verify if abbreviated
nominative and abbreviated genitive month names are the same in Silesian.  If
not, ab_alt_mon section must be provided.  See the examples:

* bug 10871
* https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2aa8009 (Polish)
* https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=189699a (Kashubian)

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

  reply	other threads:[~2019-06-18  0:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 22:27 [Bug localedata/24652] New: " gregorykkulik at gmail dot com
2019-06-18  0:23 ` digitalfreak at lingonborough dot com [this message]
2019-06-18 17:10 ` [Bug localedata/24652] " gregorykkulik at gmail dot com
2019-06-18 17:11 ` gregorykkulik at gmail dot com
2019-06-21 21:52 ` digitalfreak at lingonborough dot com
2019-06-22 10:54 ` gregorykkulik at gmail dot com
2019-06-24  9:03 ` cvs-commit at gcc dot gnu.org
2019-06-24  9:48 ` digitalfreak at lingonborough dot com
2019-06-24 11:14 ` piotrdrag at gmail dot com
2019-06-24 19:59 ` digitalfreak at lingonborough dot com
2019-06-24 20:14 ` gregorykkulik at gmail dot com
2019-06-24 20:25 ` cvs-commit at gcc dot gnu.org
2019-07-26 15:29 ` jsm28 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-24652-716-uMyj6lZ6ps@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).