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

CLDR Ticket #8145(design)

Opened 4 years ago

Last modified 3 months ago

Resolve capitalization data/structure

Reported by: mark Owned by: pedberg
Component: to-assess Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


For background and details, see https://docs.google.com/document/d/1z8gtBLbWzYk9KUKGJMS9YwOMpdOZEj6lw8AtxMOsfNw/edit?usp=sharing

  1. CLDR should have a defined value for “no-change”, instead of just using ∅∅∅.
  2. When asking people who speak different languages, it appears that the default for menus should be to titlecase_firstword: only unusual languages don't use titlecase in menus and labels. For that reason, I don't trust the above list in CLDR. We should re-vet the language settings.
  3. We might also have a global setting for all contexts other than body text, so that we can set uiListOrMenu → titlecase_firstword once for that.
  4. Also, I'm not quite sure why we need to distinguish between stand_alone and uiListOrMenu. How are they different? Isn’t a label in a uiListOrMenu really stand_alone?
  5. I had to experiment a bit to get the list of values for the context; we should have better tooling API. See below.
  6. The contextTransformUsage values also don't seem to match the CheckConsistentCasing.Category values very well. I guess that most of the Category values aren't relevant, but where there is overlap, there shouldn't be gratuitous differences, like "language" vs "languages".


Change History

comment:1 Changed 4 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to design
  • Priority changed from assess to medium
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 28
  • Owner changed from anybody to pedberg

comment:2 Changed 4 years ago by pedberg


  • For 1 we already have a separate bug
  • Related to 2 & 4, we may need to split uiListOrMenu into two behaviors depending on whether menu label has colon. Need to collect data for this in 28.
  • For 6, need to investigate and fix as necessary.

comment:3 Changed 4 years ago by emmons

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

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

comment:4 Changed 4 years ago by emmons

  • type set to data
  • Component changed from unknown to main

comment:5 Changed 4 years ago by pedberg

  • Phase changed from rc to dsub
  • Milestone changed from 28 to 29

comment:6 Changed 3 years ago by emmons

  • Milestone changed from 29 to upcoming

comment:7 Changed 4 months ago by pedberg

  • Milestone changed from upcoming to UNSCH

CLDR 34 BRS closing item, move all upcoming → UNSCH

comment:8 Changed 4 months ago by mark

  • Component changed from main to other

comment:9 Changed 3 months ago by mark

  • Component changed from other to to-assess

Add a comment

Modify Ticket

as design

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

Note: See TracTickets for help on using tickets.