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

CLDR Ticket #4971(closed data: fixed)

Opened 3 years ago

Last modified 4 days ago

Change stand-alone forms to be lowercase

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

ticket:8457

Description

We changed our policy regarding casing to use the form appropriate for inline text.

In some locales for months, weekdays, and quarters, the format forms are uppercase, and the stand-alone forms are titlecase. The stand-alone forms should be corrected to be lowercase.

Attachments

Change History

comment:1 Changed 3 years ago by mark

  • Owner changed from anybody to pedberg
  • Priority changed from assess to major
  • Type changed from unknown to defect
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 22dres

comment:2 Changed 3 years ago by pedberg

  • Component changed from unknown to data

comment:3 Changed 3 years ago by pedberg

  • Milestone changed from 22dres to 23dsub

Can't really do this until ICU clients adopt the APIs that allow specification of context, so pushing to next version.

comment:4 Changed 3 years ago by emmons

  • Milestone changed from 23dsub to 23dres

comment:5 Changed 3 years ago by pedberg

  • Milestone changed from 23dres to 24dsub

comment:6 Changed 2 years ago by pedberg

  • Cc mark added
  • Milestone changed from 24dsub to 24dres

If the forms should always be titlecase in a stand-alone context there is no reason to change the data to lowercase.

In any case, this is still pending client adoption of the display APIs that use context. We will probably need to evaluate this in 24dres and make changes in XML if appropriate.

comment:7 Changed 2 years ago by pedberg

  • Milestone changed from 24rc to 25dsub

comment:8 Changed 21 months 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:9 Changed 21 months ago by pedberg

  • Milestone changed from 25M1 to 25rc

comment:10 Changed 19 months ago by pedberg

  • Milestone changed from 25rc to 26dsub

comment:11 Changed 16 months ago by pedberg

  • Milestone changed from 26dsub to 26dvet

comment:12 Changed 13 months ago by pedberg

  • Milestone changed from 26dvet to 27dvet

This is planned for CLDR 27

comment:13 Changed 13 months ago by pedberg

  • Milestone changed from 27dvet to 27dsub

comment:14 Changed 12 months ago by markus

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

comment:15 Changed 6 months ago by pedberg

  • Milestone changed from 27 to 28

This is to consider before starting the next Survey Tool data collection

comment:16 Changed 4 months ago by markus

  • Type changed from defect to data

comment:17 Changed 4 months ago by srl

  • Status changed from assigned to accepted

comment:18 Changed 4 months ago by pedberg

  • Status changed from accepted to reviewing
  • Xref set to 8457
  • Review set to mark

The only notable data values in English that are currently titlecased when middle-of-sentence usage would have lowercase are some of the dates/fields/field[@type="(%A)"]/displayName values - e.g. Year, Quarter, Month, etc., but not the corresponding short versions yr., qtr., mo., etc.

In the 2015-Apr-29 CLDR meeting we agreed to lowercase all of the remaining displayName values as long as there was contextTransform data to titlecase them for standalone usage. There is; the contextTransformUsage type "calendar-field" is specifically for these display names, and for English it already specifies "titlecase-firstword" for standalone context. Note:

  • For some of these names (like "time zone", formerly "Time Zone") the preferred behavior would be a normal "titlecase"; I filed cldrbug 8457: to add that as a legitimate value.
  • The only thing that ICU does with these displayNames currently is to use them for fallback appendName processing in DateTimePattern Generator; for that usage, contextTransforms do not apple (and middle-of-sentence capitalization is probably best anyway).

So for this ticket I just updated the English field/displayName values, and adjusted the common/casing data accordingly.

comment:19 Changed 4 days ago by mark

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

Add a comment

Modify Ticket

Action
as closed
The ticket will be disowned. The resolution will be deleted. 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.