Group separator migration from U+00A0 to U+202F
Marcel Schneider via CLDR-Users
cldr-users at unicode.org
Tue Sep 18 00:17:50 CDT 2018
> I didn’t aim at making French stand out, but at correcting an error in CLDR.
So I've to confess that I did focus on French and only applied for fr-FR, but
there was a lot of work, see http://cldr.unicode.org/index/downloads/cldr-34#TOC-Growth
waiting for very few vetters. Nevertheless I also cared for English (see various tickets),
and also posted on CLDR-users in a belated P.S. that fr-CA hadn’t caught up the group
separator correction yet:
https://unicode.org/pipermail/cldr-users/2018-August/000825.html
Also I’m sorry for failing to provide appropriate feedback after beta release and to post
upstream messages urging to make sure all locales using space for group separator be
kept in synchrony.
I think the point about not splitting up all the data into locales is a very good one.
There should be a common pool so that all locales using Arabic script have automatically
group separator set to ARABIC THOUSANDS SEPARATOR (provided it actually fits all),
and those locales using space should only need to specify "space" to automatically get
the correct one, ie NARROW NO-BREAK SPACE as soon as Unicode is ready to give it
currency in that role.
Also there is a display issue in the charts, where whitespaces show up as what they are:
blanks, regardless whether they are wide or narrow, justifying or fixed-width.
Non-breaking behavior may be induced from context, but we see that other correct
behavior cannot be induced from context, given numbers were supposed to be grouped
using a justifying space, so that it only works halfway where justification is turned off (eg
in Wikipedia).
I’m posting here thinking at people not monitoring Trac:
https://unicode.org/cldr/trac/ticket/11423#comment:2
Regards,
Marcel
More information about the CLDR-Users
mailing list