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

CLDR Ticket #6867(design)

Opened 5 years ago

Last modified 2 weeks ago

Not all units are used everywhere

Reported by: kent.karlsson14@… Owned by: pedberg
Component: to-assess Data Locale:
Phase: Review:
Weeks: Data Xpath:
Xref:

ticket:6985

Description

The current data on units treat all units on an equal footing. That is however not the case in the world outside. Very few countries still use the imperial units, and some of those units did not even have any corresponding (i.e. similar) unit at all.

The units that are not in common use should be so marked in the CLDR data so that application writers don't think it is ok to use units that are not in use.

https://docs.google.com/spreadsheet/ccc?key=0Amjm59l6dv0cdEE0TTRmaU5MMWE0OXM0SUVfaHM0bFE
has indications (∅∅∅ in columns G and I) on which units should be marked as "unused". This data should be reviewed via ST upon occasion, but should still be set as initial values.

Further, even though inch lives on world-wide, it does so in a very limited context: only for approximate display screen sizes and for approximate jeans sizes). So for most locales, "inch" should be marked as "limited use".

SI, "accepted for use with SI" and time units must all be marked "common use" (default) in all locales.

Attachments

Change History

comment:1 Changed 5 years ago by emmons

  • Owner changed from anybody to pedberg
  • Status changed from new to assigned
  • type changed from unknown to enhancement
  • Component changed from unknown to design
  • Milestone changed from UNSCH to future

comment:2 follow-up: ↓ 3 Changed 5 years ago by pedberg

Develop proposal for supplemental data on which units are preferred for different types of measurements by country.
e.g. in country XX what is preferred unit for pressure, or what is preferred unit for height (cm, meters, inches, feet).

comment:3 in reply to: ↑ 2 ; follow-up: ↓ 4 Changed 5 years ago by kent.karlsson14@…

Replying to pedberg:

Develop proposal for supplemental data on which units are preferred for different types of measurements by country.
e.g. in country XX what is preferred unit for pressure, or what is preferred unit for height (cm, meters, inches, feet).

This seems to be heading in the wrong direction, and risk being delayed or lost in an obscure corner of CLDR. Please stay with the original proposal in this ticket; that is very similar to the "commonly used" attribute that timezone data used to have, and the data should be present in the "main" locale files.

comment:4 in reply to: ↑ 3 Changed 5 years ago by pedberg

Replying to kent.karlsson14@…:

Replying to pedberg:

Develop proposal for supplemental data on which units are preferred for different types of measurements by country.
e.g. in country XX what is preferred unit for pressure, or what is preferred unit for height (cm, meters, inches, feet).

This seems to be heading in the wrong direction, and risk being delayed or lost in an obscure corner of CLDR. Please stay with the original proposal in this ticket; that is very similar to the "commonly used" attribute that timezone data used to have, and the data should be present in the "main" locale files.

Well, the CLDR TC did not support having such a "commonly used" attribute, and instead preferred having supplemental data of the form described above (I was just noting the outcome of the CLDR discussion). And having it in the main locales files suggests that it is an attribute of language as much as region, which seems unlikely...

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

Then I find it highly preferable to use ∅∅∅ in the "main" files for imperial units in most locales, including "en" (i.e. "en_001") as in columns G and I in the spreadsheet.

comment:6 Changed 5 years ago by emmons

  • Milestone changed from future to UNSCH

Merging future and UNSCH

comment:7 Changed 5 years ago by srl

  • Xref set to 6985

ticket:6985 for the "∅∅∅" in UI

comment:8 Changed 4 years ago by emmons

  • Status changed from assigned to design
  • Component changed from design to unknown

Updating all component design bugs to status design and component = "unknown". Please update the component as appropriate.

comment:9 Changed 2 weeks ago by mark

  • Component changed from unknown to to-assess
View

Add a comment

Modify Ticket

Action
as design
Author


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

 
Note: See TracTickets for help on using tickets.