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

CLDR Ticket #5209(accepted data)

Opened 5 years ago

Last modified 21 months ago

Names for script Zyyy "Common"

Reported by: pedberg Owned by: pedberg
Component: main Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

Script code Zyyy is designated "Code for undetermined script" by ISO 15924, and currently has the English name "Common" in CLDR. It is used for characters such as punctuation and symbols whose usage is shared among multiple scripts.

cldrbug 5188: included an Apple proposal to change the Chinese (zh) name for script Zyyy from "通用" = "common" to "通用文字" "common script", and Google agreed with that proposal. However Yoshito pointed out in e-mail discussion that this had the sense of "commonly used script" or "widely used script", which was not really the intended meaning.

He suggested that the current CLDR English name "Common" is misleading and leads to incorrect translations, since the straight translation into Japanese/Chinese as "通用" also has the sense of "widespread". He thought "Shared" might be better; Peter suggested "Multiple scripts" as another possibility. Yoshito mentioned that the translation of "Shared" into Japanese (and probably Chinese) would be "共用" which has the sense of "used by multiple different systems" .

Attachments

Change History

comment:1 Changed 5 years ago by emmons

  • Owner changed from anybody to pedberg
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 23

comment:2 Changed 5 years ago by pedberg

  • Milestone changed from 23 to 23dres

comment:3 Changed 4 years ago by pedberg

  • Milestone changed from 23dres to 24dsub

comment:4 Changed 4 years ago by pedberg

  • Milestone changed from 24dsub to 24dsub2

Should discuss among vetters, reach agreement in Survey Tool. Keeping this to start the discussion.

comment:5 Changed 4 years ago by pedberg

But we need to first decide whether there is a more suitable English name.

comment:6 Changed 4 years ago by pedberg

  • Milestone changed from 24dsub2 to 25dsub

comment:7 Changed 4 years ago by emmons

  • Milestone changed from 25dsub to 25M1

Moving all 25dsub to 25M1. Please adjust the milestone if you are not planning to complete the item in the 25M1 time frame.

comment:8 Changed 3 years ago by pedberg

  • Milestone changed from 25M1 to 25rc

comment:9 Changed 3 years ago by pedberg

  • Milestone changed from 25rc to 26dsub

comment:10 Changed 3 years ago by pedberg

  • Milestone changed from 26dsub to 26dvet

comment:11 Changed 3 years ago by pedberg

  • Milestone changed from 26dvet to 27dvet

comment:12 Changed 3 years ago by pedberg

  • Milestone changed from 27dvet to 27dsub

comment:13 Changed 3 years ago by markus

  • Phase set to dsub
  • Milestone changed from 27dsub to 27

comment:14 Changed 2 years ago by pedberg

  • Milestone changed from 27 to 28

comment:15 Changed 2 years ago by markus

  • Type changed from defect to data

comment:16 Changed 2 years ago by srl

  • Status changed from assigned to accepted

comment:17 Changed 23 months ago by pedberg

  • Priority changed from assess to medium
  • Milestone changed from 28 to 29

comment:18 Changed 21 months ago by emmons

  • Milestone changed from 29 to upcoming

Auto move of all 29 -> upcoming

View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.