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

CLDR Ticket #10252(reviewfeedback data)

Opened 10 months ago

Last modified 5 weeks ago

3 Subdivisions in ST

Reported by: mark Owned by: mark
Component: other Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


We don't require any subdivision names (outside of English) except for England, Scotland, Wales. For those we do need to gather the data for moderate coverage locales, but it doesn't show up in the Survey Tool.

We are already covered for v31 modern-coverage locales, such as subdivisions/af.xml:

<subdivision type='gbeng'>Engeland</subdivision>
<subdivision type='gbsct'>Skotland</subdivision>
<subdivision type='gbwls'>Wales</subdivision>

Given the late date, and the fact that we already have them for v31 modern-coverage locales, I suggest that we not add those to the Survey Tool this cycle, but that we just gather the data manually for new moderate or modern coverage locales.

For the future, we need to

  1. Add these three to /subdivisions/root.xml
  2. Add coverage setting to moderate for these three.

Options: we need to settle on an option for how to deal with these in the ST.

  1. Move those three subdivisions line from each /subdivisions files into the /main files, or
  2. Add the /subdivisions folder to the set accessed from the ST, like annotations

Option a is a kludge, but allows us to avoid reading all the subdivision names from en.xml into the ST, which would overload ST (a lot).


Change History

comment:1 Changed 10 months ago by emmons

  • Status changed from new to accepted
  • Component changed from unknown to other
  • Priority changed from assess to medium
  • Milestone changed from UNSCH to 33
  • Owner changed from anybody to mark
  • Type changed from unknown to data

comment:3 Changed 5 weeks ago by mark

  • Status changed from accepted to reviewfeedback

comment:4 Changed 5 weeks ago by mark

  • Milestone changed from 33 to 34

Add a comment

Modify Ticket

as reviewfeedback

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

Note: See TracTickets for help on using tickets.