"no inheritance marker"

[John Emmons]

So in the case of your example, ( en_GB for America/Los_Angeles ) - you 
hit the no-inheritance marker, which means there is no recognized short 
abbreviation for the metazone in this locale.

So per the LDML specification, the value should default to the localized 
GMT format ( i.e. "GMT-08:00" during standard time, or "GMT-07:00" during 
daylight savings ).


Regards,

John C. Emmons
Globalization Architect & Unicode CLDR TC Chairman
IBM Software Group
Internet: emmo at us.ibm.com




From:   Naoto Sato <naoto.sato at oracle.com>
To:     cldr-users at unicode.org
Date:   03/31/2015 07:06 PM
Subject:        "no inheritance marker"
Sent by:        "CLDR-Users" <cldr-users-bounces at unicode.org>



Hello,

I have a question on this "no inheritance marker", used in the short 
form of time zone "metazone" names. In LDML spec, it reads:

---
If a given short metazone form is known NOT to be understood in a given 
locale and the parent locale has this value such that it would normally 
be inherited, the inheritance of this value can be explicitly disabled 
by use of the 'no inheritance marker' as the value, which is 3 
simultaneous empty set characters ( U+2205 ). [1]
---

So if an app tries to display the short names with this marker, what 
should they actually be?

For example, in case of "en_GB" locale, lookup for "America_Pacific" 
short names ends up with this "U+2205U+2205U+2205" marker in "en_001" 
locale, which disables inheriting "PT"/"PST"/"PDT" in "en".

Naoto

[1] 
http://www.unicode.org/reports/tr35/tr35-39/tr35-dates.html#Metazone_Names
_______________________________________________
CLDR-Users mailing list
CLDR-Users at unicode.org
http://unicode.org/mailman/listinfo/cldr-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20150401/8f2d86b6/attachment.html>