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

CLDR Ticket #10832(design data)

Opened 4 months ago

Last modified 9 days ago

Many unit display names are too long

Reported by: roubert Owned by: discuss
Component: units Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

For many locales there is data like this:

<unitLength type="short">
	<unit type="digital-megabyte">
		<displayName>MByte</displayName>
		<unitPattern count="one">{0} MB</unitPattern>
		<unitPattern count="other">{0} MB</unitPattern>
	</unit>
</unitLength>
<unitLength type="narrow">
	<unit type="digital-megabyte">
		<displayName>MByte</displayName>
		<unitPattern count="one">{0}MB</unitPattern>
		<unitPattern count="other">{0}MB</unitPattern>
	</unit>
</unitLength>

Where the display name is considerably longer than would be expected for that length type and not the same as used in the formatting pattern.

Is seems as if this is not intentional:

https://unicode.org/cldr/trac/ticket/7200#comment:6

A few such display names have also already been fixed in the past (cldrbug:8805, cldrbug:9604).

Attachments

Change History

comment:1 Changed 2 weeks ago by pedberg

The display name is not necessarily supposed to be the same approximate length as the unit pattern, it is intended for a different usage. For example it might be the explanatory label for a field whose contents might be shorter and more cryptic. Basically it needs to be long enough to make clear what the unit is supposed to be, without some of the context that might be expected for the unit pattern itself.

comment:2 Changed 2 weeks ago by pedberg

  • Cc pedberg added

comment:3 Changed 9 days ago by kristi

  • Owner changed from anybody to discuss
  • Status changed from new to design
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.