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

CLDR Ticket #3971(design defect)

Opened 7 years ago

Last modified 2 months ago

Special variant tags for pseudo locales

Reported by: mark Owned by: mark
Component: unknown Data Locale:
Phase: Review:
Weeks: Data Xpath:


Description (last modified by mark) (diff)

Inside Google, we found it very useful to define some special Unicode language identifier variants. These are connected with pseudo-locales, which provide artificially generated messages that people can use in testing their products well before they are ready for sending to translation.

a pseudo locale that adds accents and expands the length. This combination and order of options will turn a string "Search results" Into "[Šéårçĥ réšûļţš one two]"

a pseudo Bidi locale that makes the original string behave as if it were written in Right-to-Left, Bidi letters, reversing the visual character order (e.g. English -> ‮English‬). Allows building an authentic but readable right-to-left UI that works as if it used a real right-to-left script, e.g. affecting the inline ordering of radio buttons and other controls.

Note: The base language "ar" is chosen to facilitate recognition of this locale as as an RTL locale. This pseudo locale actually presents modified data from the source locale for the product, typically English.

a pseudo locale for a "in-context" (aka "cracked") build. This adds extra invisible information to messages that can be used for in-context translation UIs.

(in-context locales may be created out of any locale supported by a product: e.g. "en-x-pscontxt", "ja-x-pscontxt", and "pt-PT-x-pscontxt")

For products that don't work with variant language subtags, we have alternative fallback codes for these:

en-XA as a fallback for en-x-psaccent.
ar-XB as a fallback for ar-psbidi.
*-XC as a fallback for *-pscontxt. E.g. "en-XC", "de-XC", etc.

We should consider recommending psaccent, psbidi, and pscontxt for IANA registration, or failing that, adding "va" type-values to Unicode Locale Identifiers (like en-u-va-psaccent)

There is no requirement that any user of CLDR support these, or that specific behavior be required of those who do.


Change History

comment:1 Changed 7 years ago by srl

We discussed this, and would like to propose that some essentially private-use CLDR variants be defined without specifying semantics. It doesn't seem that CLDR could define wildcards in the context of BCP47, but generally. private use variants could begin with 'x', and we could enumerate (explicitly) list xaa through xzz, and so be represented as, for example, en-u-va-xbi - but CLDR would not define that this had to do with bidi. Or, Google could use 'en-x-psbidi' for an entirely private use subtag.

comment:2 Changed 7 years ago by mark

  • Description modified (diff)

comment:3 Changed 7 years ago by mark

  • Description modified (diff)

comment:4 Changed 7 years ago by mark

  • Description modified (diff)

comment:5 Changed 7 years ago by mark

  • Description modified (diff)

comment:6 Changed 7 years ago by mark

  • Priority changed from assess to medium
  • Component changed from unknown to spec
  • Description modified (diff)
  • Milestone changed from UNSCH to 21

comment:7 Changed 7 years ago by mark

  • Owner changed from somebody to mark
  • Status changed from new to assigned

comment:8 Changed 6 years ago by mark

  • Priority changed from medium to major
  • Milestone changed from 21 to 22

comment:9 Changed 6 years ago by mark

  • Component changed from spec to design

comment:10 Changed 4 years ago by emmons

  • Milestone changed from future to UNSCH

Merging future and UNSCH

comment:11 Changed 3 years ago by emmons

  • Status changed from assigned to design
  • Component changed from design to unknown

Moving all design bugs to the design status and component = "unknown". Please update the component as appropriate.

comment:12 Changed 17 months ago by srl

  • Xref set to 9819

comment:13 Changed 2 months ago by srl

Is this a dup of ticket:9819 now?


Add a comment

Modify Ticket

as design

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

Note: See TracTickets for help on using tickets.