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

CLDR Ticket #10579(closed: fixed)

Opened 16 months ago

Last modified 7 weeks ago

hi: need consistent abbreviation symbol

Reported by: fredrik Owned by: fredrik
Component: other Data Locale: hi
Phase: dsub Review: kristi
Weeks: Data Xpath:


Throughout the Hindi localization in CLDR, we see the use of both . (Latin period) and ॰ (Devanagari abbreviation marker) inconsistently.

Per our vetter, the sporadic use of Latin period is likely a remnant of using typewriters where ॰ was omitted to save keyboard real-estate, but it's really not the correct symbol and in current writing it is what is used and recommended.

We should review period usage in the Devanagari data points and change it out to the proper abbreviation symbol.


Change History

comment:1 Changed 16 months ago by fredrik

  • Owner changed from anybody to fredrik
  • Priority changed from assess to major
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 32

Will fix in xml.

comment:2 Changed 15 months ago by kristi

Apparently, this was discuss in the Forum, and flagged for TC review.
It seems that the vetters agree to use ".". It's not a good reason to says that "॰" is not in the exemplar characters though..

However, here's additional information supporting "."
There are two different types of dots used - (॰) and (.). In CLDR, the (॰) was used first, and according to the Hindi grammar this is correct; however, this is not easily available on typing tools; therefore, nowadays this is not in use, and the second symbol i.e. (.) is being used everywhere.

comment:3 Changed 15 months ago by kristi

  • Cc kristi added

comment:4 Changed 15 months ago by fredrik

Checked with another Hindi expert internally and he felt quite strongly that the Devanagari period should be used, and that it's readily available on modern Hindi keyboard layouts.

comment:5 Changed 15 months ago by fredrik

  • Status changed from accepted to reviewing
  • Review set to kristi

comment:6 Changed 15 months ago by kristi

  • Status changed from reviewing to closed
  • Resolution set to fixed

Should flag this change and get a linguist review in v34.

comment:7 Changed 7 weeks ago by mark

  • Component changed from main to other

Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

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

Note: See TracTickets for help on using tickets.