Case Used To Translate Languages, Scripts, Territories, Currencies,
Deleted Component: xxx-docs
As in previous releases, the issue of the capitalization used when translating
lists have re-surfaced.
It is recognized by the TC that the lists for languages, scripts, and
territories are to be primarily used in menus, and hence, translators should
adopt the capitalization rules of the natural language that applies to menu
With the introduction of pluralized units in CLDR 1.6, it is also recognized
that for currency items, they may be equally used in menu lists and flowed text.
Hence translators should adopt the capitalization rule of the natural language
that applies best to menu lists and flowed text. It is also recognized that
this recommendation has limitations for applications wishing to use such items
in either environments.
if the translation is titlecased, there is a problem getting the
Azerbaijanian Manat => azerbaijanian manat - but it should be
Azerbaijanian manat when used in menus.
2. if the translation is lowercased, there is a problem getting titlecase:
florin des Antilles => Florin Des Antilles - but it should be Florin des
Antilles when used in menus.
Additional structure is required to better support this functionality – that
structure may exist at present, but its not currently exposed in the survey
Trac Comment 17 by —2010-11-18T03:53:03.000Z
The commits so far in this bug were all done in 2008 for CLDR 1.6. I have split off a new : for any further work, so I am closing this (the work was actually done by Mike Tardif).
Trac Comment by tardif—2009-03-12T21:17:15.000Z
Trac Comment by —2008-11-18T21:23:56.000Z
Trac Comment by —2008-06-19T18:30:44.000Z
Trac Comment by guest—2008-05-22T03:47:36.000Z
sent reply 3