RE: [Ltru] Re: Proposal: include new "Language-Type:" field

"Debbie Garside" <debbie@ictmarketing.co.uk> Thu, 05 October 2006 09:12 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVPHm-0002n4-1j; Thu, 05 Oct 2006 05:12:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVPHk-0002mz-EC for ltru@ietf.org; Thu, 05 Oct 2006 05:12:56 -0400
Received: from 132.nexbyte.net ([62.197.41.132] helo=mx1.nexbyte.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVPHj-0004tq-28 for ltru@ietf.org; Thu, 05 Oct 2006 05:12:56 -0400
Received: from web2.nexbyte.net by mx1.nexbyte.net (MDaemon PRO v9.0.5) with ESMTP id md50004866327.msg for <ltru@ietf.org>; Thu, 05 Oct 2006 10:14:50 +0100
Received: from DebbieLaptop ([83.67.121.192]) by home with MailEnable ESMTP; Thu, 05 Oct 2006 10:12:58 +0100
From: Debbie Garside <debbie@ictmarketing.co.uk>
To: ltru@ietf.org
Subject: RE: [Ltru] Re: Proposal: include new "Language-Type:" field
Date: Thu, 05 Oct 2006 10:12:35 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Thread-Index: AcboSBXwceAmsWloTnyOUp3WVwlGmQAFj98g
In-Reply-To: <004301c6e847$d0e3f440$6401a8c0@DGBP7M81>
Message-ID: <4CB5D901212D4EA6AC14672C4FA76335.MAI@home>
X-Spam-Processed: mx1.nexbyte.net, Thu, 05 Oct 2006 10:14:50 +0100 (not processed: message from valid local sender)
X-MDRemoteIP: 192.168.51.14
X-Return-Path: debbie@ictmarketing.co.uk
X-Envelope-From: debbie@ictmarketing.co.uk
X-MDaemon-Deliver-To: ltru@ietf.org
X-MDAV-Processed: mx1.nexbyte.net, Thu, 05 Oct 2006 10:14:52 +0100
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: debbie@ictmarketing.co.uk
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

+1 

> -----Original Message-----
> From: Doug Ewell [mailto:dewell@adelphia.net] 
> Sent: 05 October 2006 07:31
> To: LTRU Working Group
> Subject: [Ltru] Re: Proposal: include new "Language-Type:" field
> 
> John Cowan <cowan at ccil dot org> wrote:
> 
> > The 4646bis registry should capture the language type 
> information from 
> > ISO 639-3.  Each language, including macrolanguages, is 
> labeled in -3 
> > as either living, extinct, ancient, historic, or 
> constructed.  These 
> > terms are defined precisely at 
> http://www.sil.org/iso639-3/types.asp .
> > Though informative rather than normative, this is very 
> useful to help 
> > shrink the large number of languages to a more manageable size.
> 
> I support this proposal of John's.  I don't agree that it 
> makes the Registry into a "kitchen sink" compendium of 
> irrelevant information -- it is directly related to tagging.
> 
> We have text in Section 4.1 of 4646bis that tells users not 
> to use "subtags for language collections," but those are not 
> clearly defined anywhere except by reference to ISO 639 (and 
> by a rather puzzling passage involving "xxx" and "yyy", which 
> I guess are space-fillers). 
> One of the major reasons for having a Registry was so users 
> would not have to go back to the ISO standards to find out 
> what to use and what not to use.
> 
> Likewise, instead of having separate notes about (not) using 
> "und" and "mul", it might make sense to include a broad usage 
> note about type "special" and then list the specific cases.  
> Note that by hard-coding "und" and "mul" into 4646 and 
> 4646bis, we have missed talking about "zxx", which should 
> have similar usage constraints.
> 
> Trying to correlate languages to countries or group them into 
> families (beyond what the core standard provides) would be 
> examples of adding information that isn't needed for tagging.
> 
> It would be easy to add these Language-Type fields to the 
> 4645bis Registry based on the 639-3 data -- not to say that 
> should be a determining factor in whether we do it.
> 
> --
> Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  
> UTN #14 http://users.adelphia.net/~dewell/
> http://www1.ietf.org/html.charters/ltru-charter.html
> http://www.alvestrand.no/mailman/listinfo/ietf-languages
> 
> 
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru
> 
> 
> 
> 





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