public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: kdex <kdex@kdex.de>
To: libc-locales@sourceware.org
Subject: de_DE has been using the wrong group separator for over 18 years
Date: Tue, 17 Apr 2018 18:41:00 -0000	[thread overview]
Message-ID: <3683185.h84fTtD0bZ@punchy> (raw)

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

I have noticed that the locale `de_DE` has erroneously been using a full stop 
(U+002E) for the thousands (group) separator in `mon_thousands_sep` and 
`thousands_sep` ever since 2000. The usage of a full stop to group thousands 
has (to my knowledge) has never been standardized.

As per DIN 1333, DIN 5008, and DIN EN ISO 80000, the separator should have 
been a thin space (U+2009).

In fact, DIN 1333 even explicitly forbids the usage of U+002E to group 
thousands, and DIN EN ISO 80000 explicitly excludes all other characters than 
a thin space.

Has anyone noticed this before? I fear that this change might break a lot of 
code that relies on the separator being wrong. Yet, this really should be 
fixed…

What's the best way to deal with this?

For further information, please also refer to the relevant section on 
Wikipedia at [1] (German).

[1] https://de.wikipedia.org/wiki/
Zifferngruppierung#Zur_Problematik_von_Punkt_und_Komma_f%C3%BCr_Tausender-
_und_Dezimaltrennzeichen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-04-17 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 18:41 kdex [this message]
2018-04-17 20:53 ` Carlos O'Donell

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=3683185.h84fTtD0bZ@punchy \
    --to=kdex@kdex.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).