Re: [Ltru] extlang

Gerard Meijssen <gerard.meijssen@gmail.com> Sun, 18 March 2007 17:01 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSylZ-0005Qk-LM; Sun, 18 Mar 2007 13:01:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSylY-0005Ly-Bf for ltru@ietf.org; Sun, 18 Mar 2007 13:01:56 -0400
Received: from ug-out-1314.google.com ([66.249.92.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSylX-0005Lp-1D for ltru@ietf.org; Sun, 18 Mar 2007 13:01:56 -0400
Received: by ug-out-1314.google.com with SMTP id 72so1019549ugd for <ltru@ietf.org>; Sun, 18 Mar 2007 10:01:54 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=epErxCwimdmGsuWcPl1MG5ZnzW2RS1hfq9ARLeCOHpwX2YNcLB4j7BQJ0dR1JtgpeSvQLt+dYneZrnBmMPi0S/WFmograg7jTAMJnV/qcCiQkRX7HXajq3IzZcen83WSZOPPJ2Sm/izPEzKRdJJjObKJVvrLQMSWD7zs8Mrv+Rk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NLRxGof17jzCB3Zx1PiJ+myoYtKTC81gyX12mG7+WXW31F5EjCmcvSyTxYPs6RnFDatz0/YZ2OtDFWRTLPRZzjOLs5pn1agWYxyZTJCmYainBHBSoddURPN5wYr+jAY9UnQF1oS9j9HHnjKJxOBd4ZYjiA7BE794oQ85Dx9Luo4=
Received: by 10.67.92.1 with SMTP id u1mr8351775ugl.1174237314234; Sun, 18 Mar 2007 10:01:54 -0700 (PDT)
Received: from ?192.168.0.2? ( [62.195.155.247]) by mx.google.com with ESMTP id l40sm4254124ugc.2007.03.18.10.01.52; Sun, 18 Mar 2007 10:01:53 -0700 (PDT)
Message-ID: <45FD7058.8030409@gmail.com>
Date: Sun, 18 Mar 2007 18:01:12 +0100
From: Gerard Meijssen <gerard.meijssen@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Doug Ewell <dewell@adelphia.net>
Subject: Re: [Ltru] extlang
References: <30b660a20703171149i47d09580w126aeb3f9feb8fdf@mail.gmail.com> <45FD2D84.5050007@gmail.com> <00b801c7697d$12fa98f0$6401a8c0@DGBP7M81>
In-Reply-To: <00b801c7697d$12fa98f0$6401a8c0@DGBP7M81>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: LTRU Working Group <ltru@ietf.org>
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Hoi,
The point was if it makes sense to allow for both zh-cmn and cmn. The 
fact that some languages are considered together a single language is 
very much beside the point. I will not argue that. One point is that 
computers can easily equate these two codes as being the same.

The other point to my argument is not addressed; this is that it is 
easier to explain to people; a single code per language and for 
compatibilities sake, zh is understood to be all these languages and is 
therefore not as discrete it can be appended with the later code. Of 
importance is that in this way more content will be tagged in a way that 
is correct. When you allow for one language one tag, you make it easier 
for people to do a right thing.

Thanks,
    GerardM


Doug Ewell schreef:
> Gerard Meijssen <gerard dot meijssen at gmail dot com> wrote:
>
>> You can explain that zh is old and Mandarin can be used as zh-cmn and 
>> cmn as a consequence. People will opt for cmn if they have the option 
>> and to it right, they will still opt for cmn and you would call them 
>> wrong.
>
> This continues to be a misrepresentation of the nature and intent of 
> macrolanguages.  It is not a question of one being "old" and the other 
> being "new."  If it were, the "old" code element would not exist in 
> ISO 639-3.
>
> The ISO 639-3/RA has determined that for some languages, including 
> Chinese and I guess 53 others, it is suitable or common in some 
> situations to think of them as a single language and in other 
> situations as multiple languages.  That is the decision they have 
> made, based on their knowledge and research.  I do not consider it my 
> job, at least, to second-guess their knowledge or research about 
> Chinese and declare that it is never appropriate to think of Chinese 
> as a single language, nor to "bake" (as Mark would say) my opinion 
> into the tagging standard.
>


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru