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

CLDR Ticket #10937(accepted)

Opened 9 months ago

Last modified 3 weeks ago

Urdu inconsistent commas

Reported by: mark Owned by: kristi
Component: fix-in-survey-tool Data Locale:
Phase: dsub Review: mellie
Weeks: Data Xpath:
Xref:

Description

There appear to be inconsistent commas in Urdu.

5,043: <group>,</group>

7,987: <listPatternPart type="start">{0}, {1}</listPatternPart>
7,988: <listPatternPart type="middle">{0}, {1}</listPatternPart>

When I look at some of these, there is clearly something wrong. Notice the use of ascii commas for start and middle, and arabic comma for end.

<listPattern type="unit">

<listPatternPart type="start">{0}, {1}</listPatternPart>
<listPatternPart type="middle">{0}, {1}</listPatternPart>
<listPatternPart type="end">{0}، اور {1}</listPatternPart>
<listPatternPart type="2">{0} اور {1}</listPatternPart>

</listPattern>

We need to have our vetters pay more attention

Attachments

Change History

comment:1 Changed 9 months ago by mark

  • Priority changed from assess to major
  • type changed from unknown to tools
  • Milestone changed from UNSCH to 34

Take this, see if we can handle by being more strict about punctuation exemplars. See other tickts.

comment:2 Changed 9 months ago by mark

  • Owner changed from anybody to mark
  • Status changed from new to accepted

comment:3 Changed 9 months ago by mark

Add comment for how to communicate to vetters.

comment:4 Changed 5 months ago by mark

  • Cc mellie added; chiara removed
  • Owner changed from mark to SurveyTool
  • Review set to mellie

Mellie, this is a SurveyTool one. Can you alert people on the forum to it?

comment:5 Changed 5 months ago by mellie

Google vetter and vendor PM have been informed, thanks!

comment:6 Changed 5 months ago by mellie

Please see below the answer from our UR reviewer:

When we need to use English words in Urdu writings, for example there could be product names that do not need to be translated or person names that should stay in English, in this case we use English comma to separate English words.

English message:
User can use YouTube, Google Maps and Google Search on this computer.

Urdu translation.
‫صارف اس کمپیوٹر پر YouTube, Google Maps اور Google تلاش استعمال کر سکتا ہے۔

However, if there are Urdu words in an Urdu sentence that need to be separated, we use Urdu comma.

English Message:
I have visited London, Paris and New York.

Urdu translation:
میں نے لندن، پیرس اور نیویارک کی سیر کی ہوئی ہے۔

<listPatternPart type="start">{0}, {1}</listPatternPart>
<listPatternPart type="middle">{0}, {1}</listPatternPart>

In above examples, assumption is the placeholders will be replaced with English words, hence English comma is used.

<listPatternPart type="end">{0}، اور {1}</listPatternPart>

In above example, since it has translation of "and" in it, assumption is the placeholders will be replaced with Urdu words, hence Urdu comma is used

comment:7 Changed 5 months ago by mark

The problem is that

<listPatternPart type="start">{0}, {1}</listPatternPart>
<listPatternPart type="middle">{0}, {1}</listPatternPart>
<listPatternPart type="end">{0}، اور {1}</listPatternPart>

<listPatternPart type="2">{0} اور {1}</listPatternPart>

are used to form a single list. So a list of <A B C D E> use

start: to connect A and B
middle: to connect B and C, and C and D
end: to connect D and E

while when the list has only two elements <A B> then

"2": to connect A and B

So you really don't want to have different commas.

You see this in the example in the SurveyTool.

comment:8 Changed 4 weeks ago by pedberg

  • Milestone changed from 34 to upcoming

CLDR 34 BRS closing item, move all open 34 → upcoming

comment:9 Changed 3 weeks ago by mark

  • Owner changed from SurveyTool to kristi
  • Component changed from unknown to survey-submit

comment:10 Changed 3 weeks ago by mark

  • Milestone changed from upcoming to 35-optional
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.