Re: Armenian (was: Re: ISO 639-3 changes, part 3)

Michael Everson <[email protected]>
Newsgroups gmane.ietf.languages
Message-ID <[email protected]>
hy.wikipedia.org has hitherto been used for both, but those articles written in Western have been explicitly marked and will ALL be moved to the new hyw.wikipedia.org

I expect the same would hold true for other applications, whether bibliographical or terminological or in software like localizations or CLDR.

hy-arevela might be harmless but I don’t see the merit in retaining it.

> On 9 Mar 2018, at 02:26, Doug Ewell <[email protected]> wrote:
> 
> Michael Everson wrote:
> 
>> I don’t know who decides this one.
> 
> You do. We are talking about variants, a BCP 47 invention not dependent on any external standard.
> 
>> I can easily decide to deprecate arevmda in favour of hyw. I would be
>> inclined to deprecate arevela under the terms listed above unless
>> there is some reason not to.
> 
> Here's my reason: The fact that we are right now debating whether 'hy' has always meant both Western and Eastern Armenian, or whether it has only ever meant Eastern and there was never any way to tag Western, should show the potential for confusion that the variant 'arevela' can help alleviate.
> 
> "hyw" - means Western only
> 
> "hy" - should now be used to mean Eastern only, but may have been used in the past for Western as well, and may still continue be used that way by some
> 
> "hy-arevmda" - means Western; no longer needed now that "hyw" exists; should be deprecated
> 
> "hy-arevela" - means Eastern; could be useful to resolve possible continuing ambiguity of "hy"; recommend leaving this one alone
> 
> In a world where people continue to write "ja-JP", I think "hy-arevela" is fairly harmless.
> 
> My 0.02 ֏,

_______________________________________________
Ietf-languages mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-languages
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.