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

CLDR Ticket #6559(accepted data)

Opened 4 years ago

Last modified 20 months ago

Fix bad width cases, part 2

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

ticket:6496

ticket:6596

Description

This is split out of cldrbug 6496: for any further name width reductions that can be done, per the spreadsheet from that ticket (not updated to reflect the changes already made in cldrbug 6496:):
[​https://docs.google.com/spreadsheet/ccc?key=0AqRLrRqNEKv-dGN6Z2dITHBBWXhaY2pOV25YTk1Zc3c#gid=0]

Attachments

Change History

comment:1 Changed 4 years ago by pedberg

Update spreadsheet (perhaps in new page) to reflect only the remaining issues

File a ticket to customize the width test, possibly having different max values for different languages

comment:2 Changed 4 years ago by pedberg

  • Owner changed from anybody to pedberg
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 24rc

comment:3 Changed 4 years ago by pedberg

  • Xref changed from 6496 to 6496, 6596

Spreadsheet showing remaining too-wide items after the changes in cldrbug 6496:

(sorted by locale, not by % width difference from English)

As noted in cldrbug 6496:

  • For many of the cases either marked in red or with very large % differences from English, the items are part of a set which all have similar widths (though many of the other members are not marked in red), and the main reason these stand out is that the English value has a smaller width than other members of the English set. So for these it is the test that is the problem.
  • Many other cases are the result of translating a unit that is unfamiliar in the target language, so there is no understandable shorter form. For these we may need to customize the tests by language.

I have filed cldrbug 6596: to improve the tests to help address the above problems. Meanwhile there may be a few more data items that can be fixed.

comment:4 Changed 4 years ago by pedberg

  • Milestone changed from 24rc to 25dsub

comment:5 Changed 3 years ago by emmons

  • Milestone changed from 25dsub to 25M1

Moving all 25dsub to 25M1. Please adjust the milestone if you are not planning to complete the item in the 25M1 time frame.

comment:6 Changed 3 years ago by pedberg

  • Milestone changed from 25M1 to 25rc

comment:7 Changed 3 years ago by pedberg

  • Milestone changed from 25rc to 26dsub

comment:8 Changed 3 years ago by pedberg

  • Milestone changed from 26dsub to 26dvet

comment:9 Changed 3 years ago by pedberg

  • Milestone changed from 26dvet to 27dsub

comment:10 Changed 3 years ago by markus

  • Phase set to dsub
  • Milestone changed from 27dsub to 27

comment:11 Changed 2 years ago by pedberg

  • Milestone changed from 27 to 28

comment:12 Changed 2 years ago by pedberg

  • Phase changed from dsub to dvet

comment:13 Changed 2 years ago by markus

  • Type changed from task to data

comment:14 Changed 22 months ago by pedberg

  • Phase changed from dvet to dsub
  • Priority changed from major to medium
  • Milestone changed from 28 to 29

comment:15 Changed 20 months ago by emmons

  • Milestone changed from 29 to upcoming

Auto move of all 29 -> upcoming

View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.