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

CLDR Ticket #4016(design defect)

Opened 7 years ago

Last modified 3 years ago

Fix spurious errors related to count="0"/count="1" translations, and delete needless count="0"/count="1" translations

Reported by: kent.karlsson14@… Owned by: mark
Component: unknown Data Locale:
Phase: Review:
Weeks: 0.2 Data Xpath:
Xref:

Description

I've made a quick review of the data present in the "count=0"/"count=1" translations
in CLDR 2.0 relative to what is given as translations in the ordinary plural rules.

For the following locales, the "count=0"/"count=1" translations adds nothing worth
keeping (but may have casing and other errors):

af bg ca cs da/ de el es/ es_419 et/ fr fr_CA gl/ gu hi hr/ hu/ id is/ it/ ja/ ko lt lv
ml mr ms nb nl/ pl pt ru sk sl sr sv/ te th tr uk vi zh zh_Hant zh_Hant_HK

Those marked with / above in particular seem to have spurious errors of various kinds.
Casing errors are not noted here.

da: spurious differences dage/døgn (døgn should be preferred, also for nb&nn)
es: "dentro" really means within (though it is ambiguous with "in");

"en" (as used in 'es_419') is preferable over "dentro" also for 'es'

et: has spurious + and - in the translations
gl: has English translations
hr: count "other" sometimes uses a different formulation (with colon), which is probably undesirable
hu: seems strange; missing plural forms, or nonce differences?
is: uses spellout for "one" (count=1) but not otherwise, which should be counted as a nonce difference
it: has English translations
ja: has nonce spacing differences
nl: spurious differences dag/etmal
sv: spurious differences dag/dygn (dygn should be preferred)

hr, ru, uk: "many" should (maybe) include 0 in the plural-rules (0 is at present "other")

Needs closer review: am ar bn eu fa fi fil he kn ro sw ta ur zu

(in particular: am, bn, sw, ta, zu may have faulty plural rules;
use of spellout/similar instead of digits; other discrepancies)

Attachments

Change History

comment:1 Changed 7 years ago by mark

  • Owner changed from somebody to mark
  • Priority changed from assess to major
  • Status changed from new to assigned
  • Component changed from data to design
  • Milestone changed from UNSCH to 21

Come up with proposal for handling.

comment:2 Changed 6 years ago by mark

  • Keywords google added

comment:3 Changed 6 years ago by mark

  • Weeks set to 0.2
  • Milestone changed from 21 to 22

comment:4 Changed 4 years ago by emmons

  • Milestone changed from future to UNSCH

Merging future and UNSCH

comment:5 Changed 3 years ago by emmons

  • Status changed from assigned to design
  • Component changed from design to unknown

Moving all design bugs to the design status and component = "unknown". Please update the component as appropriate.

View

Add a comment

Modify Ticket

Action
as design
Author


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

 
Note: See TracTickets for help on using tickets.