Skip to main content

Search and Top Navigation

#8523 closed bug (notabug)

Opened August 27, 2012 09:11AM UTC

Closed September 12, 2012 08:43AM UTC

Tamil Calendar localisation is incorrect

Reported by: Shanmuga Owned by: Shanmuga
Priority: minor Milestone: 1.9.0
Component: ui.datepicker Version: 1.8.23
Keywords: Cc:
Blocked by: Blocking:

Tamil month name is not translated instead it is in tamil calendar actual month. It is not August = Avani(tamil month)


Attachments (0)
Change History (4)

Changed August 27, 2012 12:12PM UTC by scottgonzalez comment:1

component: ui.coreui.datepicker
owner: → Shanmuga
status: newpending

Can you please provide more detail than this? Are you saying that the month names we're using apply only to the Tamil calendar and not the Gregorian calendar? It looks like CLDR has different values listed:

Can you confirm that the values in CLDR are what you expect? Also, I'm not sure when to use the format context or the stand-alone context, so if you could specify which values should be listed that would be helpful. Of course, the most helpful thing you could do is to send a pull request with the corrected values.

Changed August 28, 2012 06:15AM UTC by Shanmuga comment:2

status: pendingnew

Tamil month names used in calendar is not the translated instead you have used tamil months. It is different.

Use "ஆகஸ்டு 2012" instead of "ஆவணி 2012" in your demo:

Thanks for the good work!

Changed August 28, 2012 11:52AM UTC by scottgonzalez comment:3

status: newpending

To clarify, you're saying we should use the stand-alone wide months from CLDR? What should we be using for monthNamesShort? Are the day names all correct?

Changed September 12, 2012 08:43AM UTC by trac-o-bot comment:4

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!