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

CLDR Ticket #11360(reviewing)

Opened 3 months ago

Last modified 10 days ago

Add collision test for typographic terms

Reported by: mark Owned by: mark
Component: units Data Locale:
Phase: dsub Review: pedberg
Weeks: Data Xpath:
Xref:

Description

I just saw the following both translated as "ultrafett". That is not a problem, but we should check that the names can only collide IF the internal values (eg wght-950) are identical.

wght-950-ultrablack
wght-950-ultraheavy

That is, we wouldn't want wght-900-heavy to also be translated as "ultrafett". The code may do this already (though I suspect not).

Attachments

Change History

comment:1 Changed 2 weeks ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to major
  • Status changed from new to accepted
  • Component changed from unknown to units
  • Milestone changed from UNSCH to 35-optional

comment:2 Changed 10 days ago by mark

  • Cc kristi, fredrik, mellie, rachele added
  • Milestone changed from 35-optional to 35

Note: there were about 120 collisions in the data that people will need to fix.

Suggested additions to the hub:

Typographic Names
These are names given to different variants of a font. The most common problem is giving the same name to two different fields. For example, you mustn't give the same name to wdth-50 and wdth-100.

Axis

  1. Slant is different than italic (in the latter, the characters are slanted, but also usually different shapes)

Style

  1. The wdth-100 and wght-400 (which are normal and regular in English) must have different names: normal is width (how wide the character is), and regular is boldness (how heavy the lines in the character are). If there is not a distinction in your language, you can qualify, eg normal-width
  2. Similarly wdth-125 and wght-700 (in English: wide and bold) need to be different (width vs boldness)
  3. However, only the first two parts of the code make a difference (up to the number). The last part (after the number) is purely optional. You only need to have different names for the optional ones if your language really has alternative names for the same feature. That means that you can give the same names to each of the following:
    • wdth-50
    • wdth-50-compressed
    • wdth-50-narrow

comment:3 Changed 10 days ago by mark

  • Status changed from accepted to reviewing
  • Review set to pedberg
View

Add a comment

Modify Ticket

Action
as reviewing
Author


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

 
Note: See TracTickets for help on using tickets.