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

CLDR Ticket #8239(closed: fixed)

Opened 4 years ago

Last modified 4 months ago

Need English names for line break keyword "lb" and its values

Reported by: pedberg Owned by: pedberg
Component: other Data Locale:
Phase: final Review: emmons
Weeks: Data Xpath:
Xref:

ticket:4931

ticket:8247

Description (last modified by pedberg) (diff)

Per cldrbug 4931:, a new BCP47 -u- extension keyword "lb" (line break type) was added, with three possible values defined so far: strict, normal, loose. We need to add English names for these in the <types> element, and make sure they are exposed for modern coverage.

Attachments

Change History

comment:1 Changed 4 years ago by pedberg

  • Owner changed from anybody to pedberg
  • Priority changed from assess to critical
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 27

comment:2 Changed 4 years ago by pedberg

  • Status changed from accepted to reviewing
  • Xref changed from 4931 to 4931 8247
  • Description modified (diff)
  • Summary changed from Need English names for values of the line break keyword "lb" to Need English names for line break keyword "lb" and its values
  • Phase changed from dsub to final
  • Review set to emmons

To minimize changes: Moved the coverage part to cldrbug 8247: since that can be for CLDR 28

comment:3 follow-up: ↓ 4 Changed 4 years ago by emmons

  • Status changed from reviewing to accepted

Peter -

I'm a little concerned that single words like just "Strict", "Normal", or "Loose" are likely to be taken out of context by translators. I would prefer that we spell things out by saying "Strict Line Break Style", "Normal Line Break Style", etc.

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

  • Cc andy, emmons added

Replying to emmons:

Peter -

I'm a little concerned that single words like just "Strict", "Normal", or "Loose" are likely to be taken out of context by translators. I would prefer that we spell things out by saying "Strict Line Break Style", "Normal Line Break Style", etc.

Understood. I was thinking of it from the client side. At Apple, for example, things like this would be in a menu labeled "LIne Break Style" so repeating that in each item would be redundant (we have the same issue with names for calendars and collations). But for translators I can see it.

I think it would actually be more clear as :
strict = "Fewer Line Break Opportunities"
normal = "Normal Line Break Opportunities"
loose = "Many Line Break Opportunities" or "More Line Break Opportunities"

We can review these again before 28dsub; the current values are just for this release.

Last edited 4 years ago by pedberg (previous) (diff)

comment:5 Changed 4 years ago by pedberg

  • Status changed from accepted to reviewing

Well for now I went with "Strict Line Break Style" etc. since that is straightforward. We can discuss alternatives before 28dsub.

comment:6 Changed 4 years ago by emmons

  • Status changed from reviewing to closed
  • Resolution set to fixed

comment:7 Changed 4 months ago by mark

  • Component changed from main to other
View

Add a comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.