public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
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: Tue, 21 May 2019 21:39:00 -0000	[thread overview]
Message-ID: <0976a03f-ce4b-0c94-fc75-322a3a11357e@g4t3.de> (raw)
In-Reply-To: <a030f0fe-85c7-c70f-3a2b-209a84dafcb4@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2448 bytes --]

On 5/18/19 6:22 AM, Carlos O'Donell wrote:
> On 5/17/19 7:12 PM, Jakob Runge wrote:
>> 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.
> 
> The current data in fr_CH was contributed by Keld Simonsen, and you
> should reach out to him also to discuss this issue.
> 
> 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've dug deeper and have expended my answer at StackOverflow [1].
The CLDR ticket [2] that discusses this formatting change cites, among
other sources, the CERN guide on typography [3].

This guide specifies:

> Écriture des sommes d’argent
> 
> Le nombre s’écrit par tranches de trois chiffres séparées par un espace insécable
> (pas de point ni d’apostrophe de séparation), et est suivi (et jamais précédé) de
> l’indication de la monnaie soit au long, soit en abrégé. Pour les abréviations de noms
> de monnaie, on utilise le code ISO.

Using google translate this roughly translates to:

> Writing sums of money
> 
> The number is written in three-digit increments separated by a non-breaking space
> (no point or apostrophe of separation), and is followed (and never preceded) by
> the indication of the currency is long or abbreviated. For name abbreviations
> currency, we use the ISO code.

From this I gather that indeed the `p_cs_precedes` and `n_cs_precedes`
settings for fr_CH should be adjusted.

Since I don't have further information on other *_CH locales, and the
settings for de_CH seem to coincide with the current CLDR settings it is
my believe that only fr_CH is affected by this and should therefore be
different from de_CH and not have:

> LC_MONETARY
> copy  "de_CH"
> END LC_MONETAR

All the best,
  Jakob

[1]: https://stackoverflow.com/a/56161892/448591
[2]: https://unicode-org.atlassian.net/browse/CLDR-9370
[3]:
https://translation-council-support-group.web.cern.ch/sites/translation-council-support-group.web.cern.ch/files/Guide%20Typo_FR_styleCERN.pdf


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2019-05-21 21:39 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
2019-05-21 21:39   ` Jakob Runge [this message]

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=0976a03f-ce4b-0c94-fc75-322a3a11357e@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).