Re: Adding variant subtag 'erzgeb' for Erzgebirgisch

"Doug Ewell" <doug@ewellic.org> Wed, 12 August 2009 02:58 UTC

Return-Path: <doug@ewellic.org>
X-Original-To: ietf-languages@alvestrand.no
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1B89B39E232 for <ietf-languages@alvestrand.no>; Wed, 12 Aug 2009 04:58:43 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1O1Qz7lfsVo for <ietf-languages@alvestrand.no>; Wed, 12 Aug 2009 04:58:39 +0200 (CEST)
X-Greylist: from auto-whitelisted by SQLgrey-1.6.8
Received: from pechora2.lax.icann.org (pechora2.icann.org [208.77.188.37]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 2CA3E39E22B for <ietf-languages@alvestrand.no>; Wed, 12 Aug 2009 04:58:38 +0200 (CEST)
Received: from smtpout10.prod.mesa1.secureserver.net (smtpout10-01.prod.mesa1.secureserver.net [64.202.165.235]) by pechora2.lax.icann.org (8.13.8/8.13.8) with SMTP id n7C2wHnx031318 for <ietf-languages@iana.org>; Tue, 11 Aug 2009 19:58:37 -0700
Received: (qmail 8499 invoked from network); 12 Aug 2009 02:58:16 -0000
Received: from unknown (67.166.27.148) by smtpout10.prod.mesa1.secureserver.net (64.202.165.235) with ESMTP; 12 Aug 2009 02:58:14 -0000
Message-ID: <4568E14C3A6A4494B7D4AD997F969789@DGBP7M81>
From: Doug Ewell <doug@ewellic.org>
To: ietf-languages@iana.org
References: <mailman.15814.1250028829.5006.ietf-languages@alvestrand.no>
Subject: Re: Adding variant subtag 'erzgeb' for Erzgebirgisch
Date: Tue, 11 Aug 2009 20:58:09 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.0 (pechora2.lax.icann.org [208.77.188.37]); Tue, 11 Aug 2009 19:58:37 -0700 (PDT)
X-BeenThere: ietf-languages@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Language tag discussions <ietf-languages.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/ietf-languages>
List-Post: <mailto:ietf-languages@alvestrand.no>
List-Help: <mailto:ietf-languages-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 02:58:43 -0000

CE Whitehead <cewcathar at hotmail dot com> wrote:

> Normally I agree on this, and I am probably going to defer to Thomas 
> Goldammer on this matter; but the more I think about it the more it 
> makes sense to register this subtag with a prefix [gem] and then wait 
> for research to add a second prefix; [gem] is now a collection code, 
> right?  So using [gem] as the prefix will enable matching algorithms 
> to work.

So just to hammer the point home in a somewhat different way from Randy 
and Kent:

In order for this to work,

1. the exact set of individual languages covered under each "collection" 
subtag would have to be defined somewhere, preferably by one of the ISO 
639 registration authorities, and

2. this information would have to be reflected in the Language Subtag 
Registry, and

3. either RFC 4647 or draft-4646bis would have to have been written to 
specify that matching engines should associate collection subtags with 
the individual languages covered therein.

Since none of these is true -- unlike the situation with macrolanguages 
and extlangs -- using "gem" as the prefix will not enable matching 
algorithms to work.

Later:

> Hi.  I was hoping that [gem] would have become something like a 
> macro-language (now that 'other' is removed from its definition). 
> Apparently it is not doing so.

Removing "(other)" has nothing to do with it.  The individual languages 
covered under what ISO 639-5 calls "remainder groups" weren't subject to 
this behavior either.

> However, I am fine with registering a prefix of [de] and then adding 
> either of the other two prefixes ([sxu] or [vmf]).  (But again this 
> involves registering two prefixes, first [de] and then a second more 
> specific prefix--which Kent Karlsson seems to object to doing???)

(I think maybe CE is filtering my repeated posts on this topic.)

Once again... Creating TWO language tags for the same dialect, which is 
exactly what we would be doing by registering two prefixes in this case, 
will not help anyone.  It will result in some Erzgebirgisch content to 
be tagged with one tag and other Erzgebirgisch content to be tagged with 
a different tag, and matching algorithms will not get that right either, 
since there is no such thing as a Preferred-Value relationship between 
prefixes.  Does anyone really want that?

> And, if there are two variants of Erzgebirgisch, then I do not see why 
> we would object to having both of the other two prefixes.

I haven't seen a scrap of evidence that anyone thinks there are two 
variants of Erzgebirgisch.  Randy made a comment that *if there were* 
two such variants, then it would be appropriate to have two tags, but he 
added specifically that he was NOT saying this was so.  Certainly I've 
never heard Thomas make such a claim.

> However, if Thomas Goldammer has only one variant he wants a subtag 
> registered for, and if he can decide which prefix it should have, then 
> . . . I am fine with this single prefix.

I think that is a wise decision.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ