From: Jakob Runge <sicarius@g4t3.de>
To: libc-locales@sourceware.org
Subject: Question regarding LC_MONETARY definitions for fr_CH and de_CH
Date: Sat, 18 May 2019 00:13:00 -0000 [thread overview]
Message-ID: <a1942f56-19a8-9a17-b065-3f66051c708e@g4t3.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1421 bytes --]
Hello,
given that I'm new to this I hope that I don't tread on anyone's toes
and have found the right place for my question.
If not I'd be happy for any advise.
I've recently stumbled [1] over the LC_MONETARY definitions for fr_CH
and because fr_CH copies these from de_CH also over the ones from de_CH.
If I'm not completely mistaken these seem to be located in
'localedata/locales/fr_CH' and 'localedata/locales/de_CH' respectively.
When comparing the 'p_cs_precedes' and 'n_cs_precedes' settings against
the pages [2,3] from the unicode cldr survey-tool [4] I found what to
appears to be a mismatch to me for fr_CH.
That is for fr_CH the currency format in the CLDR appears to be defined
as '#,##0.00 ¤' which would be '1 295.00 CHF' or '-1 295.00 CHF',
but for 'localedata/locales/fr_CH' the values of 'p_cs_precedes' and
'n_cs_precedes' would be 1 on the current master commit (1f50f2a).
If my observations are correct it would seem to me that the
'p_cs_precedes' and 'n_cs_precedes' for fr_CH should be adjusted.
I'd love to read confirmation or correction on this.
All the best,
Jakob
[1]: https://stackoverflow.com/q/56057751/448591
[2]:
https://st.unicode.org/cldr-apps/v#/fr_CH/Number_Formatting_Patterns/24a93b3d14ba17b2
[3]:
https://st.unicode.org/cldr-apps/v#/de_CH/Number_Formatting_Patterns/53687a25c19b6481
[4]: http://cldr.unicode.org/index/survey-tool
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-05-18 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 0:13 Jakob Runge [this message]
2019-05-18 4:22 ` Carlos O'Donell
2019-05-18 7:16 ` Jakob Runge
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=a1942f56-19a8-9a17-b065-3f66051c708e@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).