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

CLDR Ticket #11174(closed: fix-in-surveytool)

Opened 6 months ago

Last modified 5 months ago

A meridiem value in some locales

Reported by: goun.lee@… Owned by: anybody
Component: datetime Data Locale:
Phase: dsub Review: fredrik
Weeks: Data Xpath:
Xref:

Description

Hi,I work for LG Electronics. We use CLDR data for developing a platform. and We've got some locale data change feedback through the LG local office.
I'm going to create some tickets to report here. I want to discuss if those are acceptable to CLDR.

Here's suggestion for meridiem values.

as/ca-gregorian.json -> dayPeriods.format.wide

"am" : "AM"
"pm" :"PM"

bs-Latn/ca-gregorisn.json -> dayPeriods.format.wide

"am" : "poslijepodne"

sq-AL/ca-gregorisn.json -> dayPeriods.format.wide

"am": "të paradites"
"pm": "të pasdites"

sq-ME/ca-gregorisn.json -> dayPeriods.format.wide

"am": "të paradites"
"pm": "të pasdites"

Especially, India locale(bn-IN,gu-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,ta-IN,te-IN,ur-IN,as-IN,hi-IN), We are asked to change meridiem value for AM/PM instead their own language.

ta/ca-gregorian.json -> dayPeriods.format.wide

"am" :"AM"
"pm" :"PM"

mr/ca-gregorian.json -> dayPeriods.format.wide

"am" :"AM"
"pm" :"PM"

pa/ca-gregorian.json -> dayPeriods.format.wide

"am" :"AM"
"pm" :"PM"

hi/ca-gregorian.json -> dayPeriods.format.wide

"am" :"AM"
"pm" :"PM"

Attachments

Change History

comment:1 Changed 6 months ago by goun.lee@…

Another India locale,kn-IN also need to same change/

kn/ca-gregorian.json -> dayPeriods.format.wide
"am" :"AM"
"pm" :"PM"

comment:2 Changed 6 months ago by fredrik

  • Status changed from new to closed
  • Resolution set to fix-in-surveytool
  • Review set to fredrik

Added forum posts in all these locales to highlight this ticket, except sq_ME since the locale is invalid. Assuming sq_MK is intended, but that one inherits from main sq so we should be fine.

comment:3 Changed 6 months ago by amanpreet.alam@…

for Panjabi/Punjabi (pa_*), Translation is making sense and it is better than copy of Source (English) Language. If person is using phone or Software in Panjabi, why should he read content in non-Panjabi. I am using devices from long time and there is no issue to use translated form of AM/PM although this is not perfect for Indian language, but this can't be reason to use same as Source (English).

comment:4 Changed 6 months ago by amanpreet.alam@…

Punjabi Terms are proper short localization of meaning of AM (ante meridiem - means before noon) (ਪੂ.ਦੁ. ਪੂਰਵ ਦੁਪਹਿਰ) and PM (post meridiem means after noon) (ਬਾ.ਦੁ. (ਬਾਅਦ ਦੁਪਹਿਰ)
Following is Oxford definition for AM (same for PM):
AM - Before noon (used after times of day between midnight and noon that are not expressed using the 24-hour clock)

Punjabi Standard Dictionary (Punjabi University dictionary, 7th edition) reference:
A.M. abbr (L) Ante meridiem ਦਾ ਸੰਖੇਪ, ਪੂਰਵ ਦੁਪਹਿਰ

I strongly oppose to change back to Source language. Please keep in Local language for CLDR. Companies can keep in English for their device if they want.

comment:5 Changed 6 months ago by jimidar@…

In Punjabi, I'll always prefer Locale, Instead of English. It was okay to use AM/PM only if we did not have the Punjabi Translation for these. But as we have the terms, then why to force English. Just because one private company thinks that it's suitable to their desires, does not mean we abandon our language and start speaking/writing/using some other language. It can not be forced upon us.
ਪੂ.ਦੁ. ਪੂਰਵ ਦੁਪਹਿਰ) for AM
ਬਾ.ਦੁ. (ਬਾਅਦ ਦੁਪਹਿਰ) for PM
are good enough for now. Otherwise I would go one step further and start demanding the time cycle to be divided into six (6) different portions as it is in Punjabi.
1). ਤੜਕਾ/ਤੜਕੇ, ਪਹਿਲਾ/ਪਹਿਲੇ ਪਹਿਰ
2). ਸਰਘੀ/ਪਹੁਫੁਟਾਲਾ, ਸਵੇਰੇ
3). ਦੁਪਿਹਰ, ਸ਼ਾਹ ਵੇਲਾ
4). ਤਰਕਾਲਾਂ, ਸ਼ਾਮਾਂ, ਆਥਣ/ਆਥਣੇ, ਲੌਢੇ ਵੇਲੇ
5). ਰਾਤੀਂ
6). ਅੱਧੀ ਰਾਤੀਂ/ਰਾਤ

So English speaking/favouring people will not stop their extremism of enforcing English upon us, We wont have alternative than to promote our pure language.
Please don't drag the matter to those extremes. I know you all are educated and enlightened people. Please try to save the sanity of a language.

Thanks

comment:6 Changed 5 months ago by goun.lee@…

Regarding Punjabi, We thought it was also one of reliable data because we received feedback from the local office. I was only offering opinions. If many do not agree with my suggestion, It should not be reflected in the CLDR.

and Regarding sq-ME locale, I thought it's a valid form. I checked it http://schneegans.de/lv/?tags=sq-ME&format=text.

comment:7 follow-up: ↓ 8 Changed 5 months ago by doug@…

Regarding sq-ME locale, I thought it's a valid form. I checked it ​http://schneegans.de/lv/?tags=sq-ME&format=text.

That just checks whether the tag is a valid BCP 47 tag. It doesn't mean there is a CLDR locale for Albanian for Montenegro. Your AM/PM data is the same for both 'sq-AL' and 'sq-ME', so if approved, it would just go in 'sq'.

comment:8 in reply to: ↑ 7 Changed 5 months ago by goun.lee@…

I get it. thank you for additional explanation!
Replying to doug@…:

Regarding sq-ME locale, I thought it's a valid form. I checked it ​http://schneegans.de/lv/?tags=sq-ME&format=text.

That just checks whether the tag is a valid BCP 47 tag. It doesn't mean there is a CLDR locale for Albanian for Montenegro. Your AM/PM data is the same for both 'sq-AL' and 'sq-ME', so if approved, it would just go in 'sq'.

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.