[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #6858(closed: needs-more-info)

Opened 5 years ago

Last modified 5 years ago

check for consistent "space" grouping separators; consider U+202F Narrow No-Break Space

Reported by: markus Owned by: anybody
Component: unknown Data Locale:
Phase: Review:
Weeks: 0.1 Data Xpath:


Some countries use a "no-break space" as a number grouping separator ("thousands separator"). Unicode has three no-break spaces (they don't seem to do well when pasted into Trac):

  • U+00A0 ( ) NO-BREAK SPACE
  • U+2007 (   ) FIGURE SPACE

We should have Survey Tool code in place to ensure that we use a consistent character.

On a hunch, I asked cldr-users whether Figure Space would be more appropriate than the No-Break Space that we currently use. Both Kent Karlsson and Philippe Verdy responded that the grouping separator space should be "narrow". Both explicitly argued against Figure space, and Philippe recommends using the Narrow No-Break Space rather than the Latin-1 No-Break Space.


Change History

comment:1 Changed 5 years ago by kent.karlsson14@…

This [NNBSP or NBSP] applies not only to the grouping separator, but also to the space between a number and a unit (currency, time, length, speed, ...). They are currently ordinary space in CLDR, which they should not be.

comment:2 Changed 5 years ago by kent.karlsson14@…

For the space before unit symbols, see ticket:6860.

comment:3 Changed 5 years ago by pedberg

CLDR does already automatically normalize spaces in given positions to given types (in some positions, all spaces are converted to NO-BREAK SPACE, in other positions they are converted to regular SPACE).

comment:4 Changed 5 years ago by mark

  • Status changed from new to closed
  • Resolution set to needs-more-info

We do already normalize to either space or NBSP. Are there fields in particular that are causing problems? (other than ticket:6860)?


Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.