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

CLDR Ticket #10777(closed spec: fixed)

Opened 11 months ago

Last modified 2 weeks ago

Really document diff between defaultContent, likelySubtags, &locale-matching

Reported by: mark Owned by: mark
Component: other Data Locale:
Phase: spec-beta Review: pedberg
Weeks: Data Xpath:
Xref:

Description

There is a significant difference among each of the following:

  1. inheritance in CLDR (which can be pragmatic, to get the easiest way to share data) [defaultContent]
  2. addLikelySubtag, which gives you the most likely full subtag in the absence of other information [likelySubtags.xml]
  3. LocaleMatcher data, which provides the best match for the user's language(s) in an application's supported languages. [languageInfo.xml]

It is important that implementations of CLDR clearly understand the difference and make it clear to their users, but it is a bit tricky to dig that out of the spec.

Maybe an FAQ??

Attachments

Change History

comment:1 Changed 10 months ago by mark

  • Status changed from new to accepted
  • Cc kristi added
  • Priority changed from assess to medium
  • Phase changed from dsub to spec-beta
  • Milestone changed from UNSCH to 33
  • Owner changed from anybody to mark
  • Type changed from unknown to spec

Have new section explaining differences, and point to it from other sections.

comment:3 Changed 9 months ago by kristi

Please include clarification on how to identify the script for a locale with multiple scripts, with no script info in the locale code?

Take ccp-IN and ccp-BD, how should a program know it's in Beng or Cakm script?

• The Script information in the supplementaldata specifies <language type="ccp" scripts="Beng Cakm"/>
• ccp data or the locale code for Ccp-IN and ccp-BD do not specify the script information.
• The only place, it’s Cakm is specified is the default Numbering system <defaultNumberingSystem>cakm</defaultNumberingSystem>
• In ccp.xml, it’s specified as <language type="ccp"/>, but doesn’t specify which script this is in.

comment:4 Changed 9 months ago by kristi

  • Cc jeff added

comment:5 Changed 9 months ago by kristi

  • Cc jefgen added; jeff removed

comment:6 Changed 7 months ago by mark

  • Type changed from spec to site

comment:7 Changed 7 months ago by mark

  • Phase changed from spec-beta to dsub

comment:8 Changed 7 months ago by emmons

  • Milestone changed from 33 to 34

comment:9 Changed 5 months ago by mark

  • Phase changed from dsub to rc

comment:10 Changed 8 weeks ago by mark

  • Type changed from site to spec
  • Component changed from unknown to other

comment:11 Changed 8 weeks ago by mark

  • Phase changed from rc to spec-beta

comment:12 Changed 2 weeks ago by mark

  • Status changed from accepted to reviewing
  • Review set to pedberg

comment:13 Changed 2 weeks ago by pedberg

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

This is very useful, thanks.

View

Add a comment

Modify Ticket

Action
as closed
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.