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

CLDR Ticket #6511(closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

zhuyin tones tailored too strong?

Reported by: markus Owned by: pedberg
Component: collation Data Locale: zh
Phase: Review: markus
Weeks: 0.1 Data Xpath:
Xref:

Description

The Chinese/zhuyin tailoring creates a secondary CE for the first tone, but primary CEs (which sort below spaces) for the other tones. Is this a mistake? Should they all be secondary CEs?

# ZHUYIN TONES (SPACING)
&[last primary ignorable]<<ˉ # zhuyin first tone, equivalent to unmarked

<ˊ<ˇ<ˋ<˙ # zhuyin fifth tone, neutral (unmarked in pinyin)

<˪ # zhuyin tone special for non-mandarin
<˫ # zhuyin tone special for non-mandarin

Attachments

Change History

comment:1 Changed 5 years ago by markus

  • Cc claireho added

I checked with my colleague Claire, a native of Taiwan. She thinks the tones should have secondary CEs, ignorable on primary level.

comment:2 Changed 5 years ago by markus

Claire also says that the "first tone" is not written, and she does not know the symbol "ˉ". Wikipedia does not mention it either, the "Tones" comparison table shows no mark: https://en.wikipedia.org/wiki/Bopomofo

FYI, Wikipedia lists the "non-mandarin" tones as "Tone symbols for Taiwanese Hokkien".

comment:3 Changed 5 years ago by emmons

  • Owner changed from anybody to pedberg
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 24rc

comment:4 Changed 5 years ago by pedberg

  • Status changed from assigned to accepted
  • Review set to markus

Yes, the above all seems correct.

comment:5 Changed 5 years ago by markus

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

comment:6 Changed 4 years ago by emmons

  • Milestone 24rc deleted

Milestone 24rc deleted

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.