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

CLDR Ticket #11044(accepted)

Opened 8 months ago

Last modified 5 weeks ago

Odia specific language guide

Reported by: kristi Owned by: meikeh
Component: docs-translation-guide Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


Google and Microsoft vetters for Odia reached an agreement on a translation approach in CLDR in this working document.

Next step:

  1. Revise the working doc in a Translation guide format.
  2. Add a new Translation guides page and a section for Odia


Change History

comment:1 Changed 6 months ago by kristi

  • Owner changed from anybody to chiara
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 34

comment:2 Changed 6 months ago by kristi

New agreement for Odia Translation guide:

  1. Avoid the use of diacritics when transliteration is required in Oriya - diacritics can be easily understood by Oriya well-versed users, but plain transliteration (without diacritics) is more common and preferred.

Follow the General Guidelines for Country/region names:

  1. Use the most neutral grammatical form for the country/region that is natural for these two usages above. If there is no single form that can accomplish that, favor the usage within UI menus.
  2. Use the capitalization that would be appropriate in the middle of a sentence; the <contextTransforms> data can specify the capitalization for other contexts. For more information, see Capitalization.
  3. Each of the names must be unique (see below).
  4. Don't use commas and don't invert the name (eg use "South Korea", not "Korean, South").
  5. Don't use the characters "(" and ")", since they will be confusing in complex language names. If you have to use brackets, use square ones: [ and ]. (to be verified with ticket http://unicode.org/cldr/trac/ticket/11065)

comment:3 Changed 6 months ago by mark

  • Component changed from unknown to translation-guide

comment:4 Changed 6 weeks ago by mark

  • Owner changed from chiara to meikeh

Transferring to Meike...

comment:5 Changed 5 weeks ago by pedberg

  • Milestone changed from 34 to upcoming

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

comment:6 Changed 3 weeks ago by mark

  • Milestone changed from upcoming to 35-optional

Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.