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/23208] New locale - Lower Sorbian (dsb)
Date: Tue, 12 Jun 2018 20:44:00 -0000	[thread overview]
Message-ID: <bug-23208-716-wYewdxrgMP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23208-716@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
(In reply to Mike FABIAN from comment #2)
> [...]
> In CLDR,
> 
> https://unicode.org/cldr/trac/browser/trunk/common/collation/dsb.xml
> https://unicode.org/cldr/trac/browser/trunk/common/collation/hsb.xml
> 
> are *exactly* the same.

Sorry, I did not know it was so easy.

However, I have these data about the Sorbian alphabets:

1. Upper Sorbian:
https://pl.wikipedia.org/wiki/Alfabet_g%C3%B3rno%C5%82u%C5%BCycki
https://hsb.wikipedia.org/wiki/Hornjoserbski_alfabet

2. Lower Sorbian:
https://pl.wikipedia.org/wiki/Alfabet_dolno%C5%82u%C5%BCycki

The differences are minor and maybe they can be handled by the same rules. Or
maybe not: if "dź" is a separately collated digraph in Upper Sorbian then
probably it should be sorted after "d." ("." means any character) while in
Lower Sorbian "dź" would be sorted between "dz" and "dþ".

> [...]
> So we could use “copy "hsb_DE"” in glibc if we want.

For now I will leave the rules as they are in the attached file because I have
a feeling that they may be different and it will be a good beginning to develop
a separate set of rules.

> If the data in the file in this bug has been copied and pasted from
> the hsb_DE glibc locale, that should be correct as well of course.

That's what I hope for now.

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

  parent reply	other threads:[~2018-06-12 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20 15:31 [Bug localedata/23208] New: " milupo at sorbzilla dot de
2018-05-20 15:38 ` [Bug localedata/23208] " milupo at sorbzilla dot de
2018-06-08  0:02 ` digitalfreak at lingonborough dot com
2018-06-08  7:31 ` maiku.fabian at gmail dot com
2018-06-11  9:21 ` maiku.fabian at gmail dot com
2018-06-12 20:44 ` digitalfreak at lingonborough dot com [this message]
2018-06-13  7:12 ` maiku.fabian at gmail dot com
2018-06-18  9:39 ` digitalfreak at lingonborough dot com
2018-06-28 10:22 ` digitalfreak at lingonborough dot com
2018-06-29  8:52 ` digitalfreak at lingonborough dot com
2018-06-29 21:06 ` cvs-commit at gcc dot gnu.org
2018-06-29 21:19 ` digitalfreak at lingonborough dot com
2018-07-13 21:08 ` cvs-commit at gcc dot gnu.org
2018-08-01  5:58 ` 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-23208-716-wYewdxrgMP@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).