Add Likely Subtags first step

[Philippe Verdy]

For "cel-gaulish"; it should have been encoded in ISO 639-3; however this
is more probably a family of dialects, and the language is mostly
reconstructed as it was not always written in the early stages (when it was
written, it was under influence of the Roman empire; and mixed with Latin,
Greek or other regional languages or other past invaders and it's difficult
to determine if this was an effective vernacular dialect; or just the
language of some rulers or merchants).
But even before the Roman invasion (and the brutal massacre
by armies of Consul Julius Caesar before he became emperor; a massacre
highly criticized even in the Roman Senate), there was this influence and
Gaulish people were already present in many places of Europe; including in
Rome.
The grandfathered "oed" variant for "en-GB" is encodable as a standard
variant. I wonder why it was not done; but it can be kept as is.


2015-01-23 17:35 GMT+01:00 Doug Ewell <doug at ewellic.org>:

> Bérenger Enselme <berenger at enselme dot com> wrote:
>
> > In http://www.unicode.org/reports/tr35/#Likely_Subtags the first step
> > is described as canonicalization.
> >
> > The 3rd substep says to return a tag as is if it is in the <variable
> > id="$grandfathered" type="choice"> from the supplemental data.
> >
> > As far as I can tell this never happens since such tags have already
> > been replaced in the 2nd substep.
> >
> > Thinking about it more, I don't think any of the grandfathered tags
> > would actually make it to the second substep since they wouldn't pass
> > the first substep.
>
> Not all grandfathered tags have a Preferred-Value. Canonicalization
> leaves such tags unchanged. Examples include "cel-gaulish", "en-GB-oed",
> and "i-mingo".
>
> --
> Doug Ewell | Thornton, CO, USA | http://ewellic.org
>
>
> _______________________________________________
> 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/20150123/ea9e628a/attachment.html>