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

CLDR Ticket #9505(reviewing unknown)

Opened 16 months ago

Last modified 2 weeks ago

Adjust Priority Items chart

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


Description (last modified by mark) (diff)

The Priority Items is used to track progress in the ST. It could be improved to be more helpful.

  1. During Submission, it is most important to drive the Missing value to zero. But
    1. this does not need to include variants, such as en_CA. Those will inherit values from their parents, and any problems can be fixed during the Vetting phase.
    2. this does not need to include Serbian (Latin) at all, since that is generated. Swiss High german can be also autogenerated, then corrected.
  2. During Vetting, it is most important to resolve Errors, Disputed, Losing, and fix any child locale values that need it.


Change History

comment:1 Changed 16 months ago by mark

  • Description modified (diff)

comment:2 Changed 15 months ago by fredrik

  • Xref set to 9535

Item 1a is highlighted in bug:9535

comment:3 Changed 15 months ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to major
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 31

comment:4 Changed 8 months ago by mark

  • Milestone changed from 31 to 32

comment:5 Changed 3 months ago by mark

Not doing sr_Latn at this time. But the changes should fix ticket:9535 also:

I have been trying to work on the Missing section of the Dashboard for en-GB, but there seems to be an issue.
The entries that are marked as missing are only missing from CLDR cycle 29, but I have voted for the term in this cycle, cycle 30, and so has the Microsoft linguist. Can you please advise?
I have tried to add a new term in case that would remedy the situation, but when I click the green tick box in order to add a new term, no new term is created and my previous vote resets.

Last edited 3 months ago by mark (previous) (diff)

comment:6 Changed 3 months ago by mark

Reviewer: the changes should also fix ticket:9512 also. Please check and close 9512 if it does.

comment:7 Changed 3 months ago by mark

Specifically, the changes should fix 2 things.

  1. The number of Missing items in the dashboard and Priority items for sublocales (such as fr_CA) should go down (they should be at most the same as the parent locale's.
    • To check, look at the dashboard for fr and fr_CA, or other parent/child pairs.
  2. The number of Losing items should go down (no longer counts as losing you put in explicit value that is same as inherited).
    • To check, go to fr_CA, pick an item that is inherited. Add that item explicitly with + and then picking Winning.

comment:8 Changed 3 months ago by kristi

  1. Losing: Vote on Inheritance, Losing # increases, because the item is now set with Status=Contributed rather than Missing. I think your intension was to make this a Winning item if that’s the one that will be set for that locale?
  1. Missing: The total number is reset (this is your fix). However, when I add votes to Inehritance, the Missing number does not go down in the Dashboard view. For example, here’s my vote on inheritance. Missing stays at 120.

comment:9 Changed 3 months ago by mark

Good comments.

  1. Yes, some of the Missing may turn into Losing. If the user is voting for the winning value, that shouldn't happen. Can you check that?
  1. Right, the Missing vote won't go down unless you vote for an item that is also missing from the parent locale. That is, votes for inherited values won't change the missing.
    1. Note that in an ideal world, we wouldn't have translators work on the child locales until the parent locales have no Missing values. That way they can just pick the parent value if it is ok, and only otherwise add a different value.

comment:10 Changed 2 weeks ago by mark

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

Add a comment

Modify Ticket

as reviewing

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

Note: See TracTickets for help on using tickets.