From: Jakob Runge <sicarius@g4t3.de>
To: libc-locales@sourceware.org
Subject: Re: Question regarding LC_MONETARY definitions for fr_CH and de_CH
Date: Sat, 18 May 2019 07:16:00 -0000 [thread overview]
Message-ID: <55f0f3b8-6d58-b7aa-d554-a9c5af11c204@g4t3.de> (raw)
In-Reply-To: <a030f0fe-85c7-c70f-3a2b-209a84dafcb4@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]
> The current data in fr_CH was contributed by Keld Simonsen, and you
> should reach out to him also to discuss this issue.
Thanks for the pointer - I will do that!
> In general glibc tries to match published government standards about
> language locales and particularly for number formats.
>
> Quoting that CLDR is different is not a good justification. Yes, we
> are trying hard to harmonize the glibc locales with CLDR since it
> avoids confusion. However, we also need to understand which database
> has it right, and correct the other.
I understand that this makes perfectly sense and would also like to
understand the source for this both in CLDR as well as glibc.
> Are you a Swiss resident? Do you have experience with the locale
> in question?
>
No - I'm not a Swiss resident, and can't speak french - so I'm fairly
removed from fr_CH. I tried to look this up on sites of the Swiss
national bank and similar institutions but had no luck in my research.
To the extend that I could get information from Swiss people it seemed
to be conflicting and unclear whether it related to fr_CH in particular.
So no - I wouldn't say that I have particular experience with the locale
in question.
All the best,
Jakob
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-18 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 0:13 Jakob Runge
2019-05-18 4:22 ` Carlos O'Donell
2019-05-18 7:16 ` Jakob Runge [this message]
2019-05-21 21:39 ` Jakob Runge
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=55f0f3b8-6d58-b7aa-d554-a9c5af11c204@g4t3.de \
--to=sicarius@g4t3.de \
--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).