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

CLDR Ticket #11065(new site)

Opened 4 months ago

Last modified 3 months ago

Translation General guide for using [ ]

Reported by: kristi Owned by: anybody
Component: unknown Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


From the translation guide:
"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 ]."

This is in two places in the translation guide:

  1. #5 in http://cldr.unicode.org/translation/country-names#TOC-General-Guidelines
  2. 3rd bullet in http://cldr.unicode.org/translation/language-names

Spot checking this across languages it does not look like this is followed at all.
We found use of ( ), but not [ ]

We should revisit the reason to reason for this guide.


Change History

comment:1 Changed 3 months ago by pedberg

  • Cc kristi added
  • Type changed from unknown to site

The reason is that parentheses are often used when combining the name of a language with the name of a script and/or language, for example:

  • Uzbek (Latin), Uzbek (Arabic)
  • Uzbek (Afghanizstan)
  • Uzbek (Arabic, Afghanistan)

So having parentheses in the name of an individual component like language or region would be confusing when combining them. However, the actual pattern that is used to do the combining is something that is also part of the locale data, see for example http://st.unicode.org/cldr-apps/v#/en/Locale_Name_Patterns/4c3249dbb329101c

So maybe the real guidance should be that in names for language, regions, or scripts, don't use bracketing characters (parentheses or other) that are the same as what are specified in the localePattern. We could add a test for that if we do not already have one.

Last edited 3 months ago by pedberg (previous) (diff)

Add a comment

Modify Ticket

as new

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

Note: See TracTickets for help on using tickets.