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

CLDR Ticket #8143(accepted tools)

Opened 3 years ago

Last modified 3 years ago

Fix CasingInfo, locale data

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


I was looking at the casing info, and there are a few issues.

CasingInfo and CheckConsistentCasing needs to have the xml reading code separated out from the generation and testing.

The following have types that are not in Category:

dsb.xml (2 matches)
18: <casingItem type="displayName">lowercase</casingItem>
19: <casingItem type="displayName_count">lowercase</casingItem>
hsb.xml (2 matches)
19: <casingItem type="displayName">lowercase</casingItem>
20: <casingItem type="displayName_count">lowercase</casingItem>

That also means that CheckConsistentCasing is not being run on those locales.

This needs to be cleaned up so that the test is consistently run, and so that we have an overview of all the casing info.


Change History

comment:1 Changed 3 years ago by emmons

  • Owner changed from anybody to mark
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Component changed from unknown to tools
  • Milestone changed from UNSCH to 27

comment:2 Changed 3 years ago by emmons

  • Phase changed from dsub to rc

comment:3 Changed 3 years ago by mark

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

comment:4 Changed 3 years ago by mark

  • Owner changed from mark to pedberg

Another casing one....

comment:5 Changed 3 years ago by markus

  • Type set to tools
  • Component changed from tools to unknown

comment:6 Changed 3 years ago by srl

  • Status changed from assigned to accepted

comment:7 Changed 3 years ago by emmons

  • Component changed from unknown to casing

comment:8 Changed 3 years ago by pedberg

  • Milestone changed from 28 to 29

comment:9 Changed 3 years ago by emmons

  • Milestone changed from 29 to upcoming

Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.