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

CLDR Ticket #7230(closed: fixed)

Opened 5 years ago

Last modified 3 months ago

Several languages have mixed up era lengths.

Reported by: shawnste@… Owned by: pedberg
Component: other Data Locale:
Phase: dsub Review: shawn
Weeks: Data Xpath:



For example "aa" has a clearly non-abbreviated eraAbbr string (and empty eraNames)

<era type="0" draft="unconfirmed">Yaasuusuk Duma</era>
<era type="1" draft="unconfirmed">Yaasuusuk Wadir</era>

If possible, it'd be nice if these were moved to eraNames & eraAbbr created for these languages.

I don't know if there's any validation tools, but some sort of check to make sure that the abbreviated strings are < 6? characters or spitting out a warning might be nice.

It's also unclear to me if the abbreviated era is appropriate for use in a "short" date format (eg: 4/4/2014 AD). Some of the forms seem rather long for that (ni J.-C.)

Given that the "narrow" form is shorter than typically used when writing out dates, I would probably prefer that the guidance for the eraAbbr field be that it should be < 5 characters.


Change History

comment:1 Changed 5 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to test
  • Priority changed from assess to medium
  • Milestone changed from UNSCH to 26rc
  • Owner changed from anybody to pedberg
  • type changed from unknown to enhancement

comment:2 Changed 4 years ago by pedberg

  • Milestone changed from 26rc to 27dsub

comment:3 Changed 4 years ago by markus

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

comment:4 Changed 4 years ago by pedberg

  • Milestone changed from 27 to 28

comment:5 Changed 4 years ago by markus

  • type changed from enhancement to unittest
  • Component changed from test to unknown

comment:6 Changed 4 years ago by pedberg

  • Status changed from assigned to reviewing
  • type changed from unittest to data
  • Component changed from unknown to main
  • Review set to shawn

The way era name inheritance is set up, both eraNames (wide) and eraNarrow alias to eraAbbr, so if we only have one era name width supplied, it has to be eraAbbr. That is what we sometimes have names in eraAbbr that are not abbreviated..

That said, there were various problems that needed fixing under this ticket:

  • If we had data for eraNames but not eraAbbr, then I copied it to eraAbbr
  • If the names for eraNarrow were longer than the ones for eraAbbr. I either swapped them, or copied selected eraAbbr names to eraNarrow, or just deleted ll of the eraNarrow ones (so the eraser names would be used in their stead).

comment:7 Changed 4 years ago by pedberg

  • Xref set to 8427

I spun our cldrbug 8427: to add a test for era name length consistency, i.e. eraNarrow <= eraAbbr <= eraNames, and to add guidance on the max recommended length for eraAbbr names. But note there may be no conventional abbreviations in many languages for eras in many calendars; of there is no abbreviation, the full name goes in eraAbbr.

comment:8 Changed 4 years ago by pedberg

  • Cc shawn added

comment:9 Changed 4 years ago by pedberg

  • Cc emmons added

comment:10 Changed 4 years ago by shawn

IMO, if the name is "long" and there is no abbreviation it would be better to fall back to root or clip the string. If it showed up in constrained UX or something, "A.D." would be better than a localized 20 character string.

comment:11 Changed 4 years ago by pedberg

That is probably a design discussion we need to have in CLDR TC, I added it to the agenda

comment:12 Changed 4 years ago by pedberg

Mark suggested a way to address this - if we only have a long name in eraAbbr, move that to eraName and then copy a shorter eraAbbr name from parent (which may be root) before collecting ST data so it can be fixed if inappropriate. I will file a separate bug for that.

comment:13 Changed 3 years ago by shawn

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

Some of these are still "long" for a narrow form.

comment:14 Changed 3 months ago by mark

  • Component changed from main to other

Add a comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.