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

CLDR Ticket #6383(accepted data)

Opened 4 years ago

Last modified 20 months ago

Spurious commas in "and" lists, and a few other "list" issues

Reported by: kent.karlsson14@… Owned by: fredrik
Component: main Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

Based on by-type chart dated 2013-06-24 18:25:32 GMT

Regular Lists

middle English: ‹{0}, {1}

{0}, ŋ́gɛ {1} ·jgo· Likely spurious comma, by translating too literally from the American English example.

end English: ‹{0}, and {1}

{0}, {1} എന്നിവ ·ml· Really, the "and" word last?
{0}, agus {1} ·gd· Likely spurious comma, by translating too literally from the American English example.
{0}, and {1} ·en· ·fil· Likely spurious comma, by translating too literally from the American English example. "and" does no seem Filipino... The proper Filipino/Tagalog word seems to be "at".
{0}, dan {1} ·id· ·ms· Likely spurious comma, by translating too literally from the American English example.
{0}, e {1} ·it· Likely spurious comma, by translating too literally from the American English example.
{0}, kple {1} ·ee· Likely spurious comma, by translating too literally from the American English example.
{0}, ḿbɛn ŋ́gɛ {1} ·jgo· Likely spurious comma, by translating too literally from the American English example.
{0}, na {1} ·sw· Likely spurious comma, by translating too literally from the American English example.
{0}, no-{1} ·zu· Likely spurious comma, by translating too literally from the American English example. Hyphen?
{0}, u {1} ·mt· Likely spurious comma, by translating too literally from the American English example.
{0}, እና {1} ·am· Likely spurious comma, by translating too literally from the American English example.
{0}, और {1} ·hi· Likely spurious comma, by translating too literally from the American English example.
{0}, এবং {1} ·bn· Likely spurious comma, by translating too literally from the American English example.
{0}, ಮತ್ತು {1} ·kn· Likely spurious comma, by translating too literally from the American English example.
{0}، اور {1} ·ur· Likely spurious comma, by translating too literally from the American English example.
{0}، و {1} ·ar· ·fa· Likely spurious comma, by translating too literally from the American English example.

Duration Lists

end English: ‹{0}, and {1}
{0}, and {1} ·fil· Likely spurious comma, by translating too literally from the American English example. And "and" does not seem like Filipino... The proper Filipino/Tagalog word seems to be "at".
{0}, ja {1} ·fi· Definitely spurious comma, by translating too literally from the American English example.
{0}, और {1} ·hi· Likely spurious comma, by translating too literally from the American English example.
{0}، و {1} ·fa· Likely spurious comma, by translating too literally from the American English example.

Attachments

Change History

comment:1 Changed 4 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to data
  • Priority changed from assess to minor
  • Milestone changed from UNSCH to 24rc
  • Owner changed from anybody to fredrik
  • Type changed from unknown to defect

comment:2 Changed 4 years ago by fredrik

  • Milestone changed from 24rc to 25dsub

comment:3 Changed 4 years ago by emmons

  • Milestone changed from 25dsub to 25rc

Moving all 25dsub and 25design tickets to 25rc. If you plan to complete items in the 25M1 time frame, please move those tickets to 25M1.

comment:4 Changed 3 years ago by fredrik

  • Milestone changed from 25rc to 26rc

comment:5 Changed 3 years ago by pedberg

  • Milestone changed from 26rc to 27dsub

comment:6 Changed 3 years ago by markus

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

comment:7 Changed 2 years ago by fredrik

  • Milestone changed from 27 to 28

comment:8 Changed 2 years ago by markus

  • Type changed from defect to data

comment:9 Changed 2 years ago by srl

  • Status changed from assigned to accepted

comment:10 Changed 22 months ago by fredrik

  • Milestone changed from 28 to 29

Out of time for this release. Pushing out to next release where we hopefully will have more time.

comment:11 Changed 20 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.