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

CLDR Ticket #10125(closed data: fixed)

Opened 2 weeks ago

Last modified 3 hours ago

zh: pattern "1000-count-other" shouldn't exist for Asian countries

Reported by: fredrik Owned by: fredrik
Component: main Data Locale: zh, zh_Hant
Phase: dsub Review: mark
Weeks: Data Xpath:
Xref:

ticket:8773

ticket:9213

Description

Somewhere in CLDR 30's development, bug:8773 came undone. According to our internal report, Chinese does not use a thousand marker, so this current format, which would display 1.23千, is wrong:

<pattern type="1000" count="other">0千</pattern>

and should be reverted to pre-30

<pattern type="1000" count="other">0</pattern>

which makes it show 1230.

I haven't been able to find a bug that tracked changing this (bug:9213 seems to suggest its undoing, but has no commits yet - I'll comment the ticket).

Apple ref rdar://problem/30943579

Attachments

Change History

comment:1 Changed 2 weeks ago by fredrik

Found the commit, it's bug:9687 with r12740, the commit with the results of the survey tool results... so this change was made by the vetters. Will check with ours.

comment:2 Changed 2 weeks ago by mark

  • Cc chiara, kristi added
  • Owner changed from anybody to fredrik
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 31.1

comment:3 Changed 9 days ago by fredrik

Clarification from our inhouse linguist. The current form with 千 is only appropriate if there are no fractions. So 1千 should be OK, but not 1.23千. Feedback is also that the survey tool did not make this effect clear.

comment:4 Changed 6 days ago by fredrik

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

comment:5 Changed 3 hours ago by mark

  • Status changed from reviewing to closed
  • Resolution set to fixed
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.