Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

No spec text about how to order different fields in https://unicode-org.github.io/cldr/ldml/tr35.html#LocaleId_Canonicalization

Description

In https://unicode-org.github.io/cldr/ldml/tr35.html#LocaleId_Canonicalization


I have problem to understand why {V={hepburn, heploc}} is order on the top instead in the third.
the first three all have "size of union" = 2,

step 5 said


and it does not mention what will happen when there are the same size of union how to compare between different field.

Why is the output NOT

 


???

Activity

Show:

Mark Davis October 4, 2021 at 12:40 AM

Anyone else we want feedback on this from?

Mark Davis October 4, 2021 at 12:40 AM

I just looked this over, and you have a good point. In addition:

The ii line is not quite right, since the fields are L, S, R, V, but in the comment it says “en < fr” which is irrelevant to ii.

Now, the most important thing is ( i ), so that we have longer sets before shorter one. The ( ii ) is to have a determinant order, but doesn’t quite do it. Here is what I propose:

 

That would give the following table (I’ll clean up the formatting in the spec.)

languageId

i. size of union

ii. field order

iii.

{L={en}, R={GB}}

2

n/a

en < fr

{L={fr}, R={CA}}

2

 

{V={fonipa, heploc}}

2

L < V

 

{V={hepburn, heploc}}

2

n/a

fonipa < hepburn

{R={CA}}

1

n/a

 

How does this sound?

Frank Yung-Fong Tang August 21, 2021 at 12:47 AM

ping? what is the status of this?

Mark Davis April 5, 2021 at 5:21 PM

Will check to see if this is an issue, and if so, whether we can slide it into v39 (very late for that, however).

Fixed

Details

Components

Priority

Fix versions

Assignee

Reviewer

Reporter

Created March 29, 2021 at 6:49 PM
Updated October 19, 2021 at 7:34 AM
Resolved October 19, 2021 at 7:34 AM