RE: [Ltru] RE: ISO 639-2 decision: "mis"

"Debbie Garside" <debbie@ictmarketing.co.uk> Fri, 15 June 2007 22:20 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 1HzK9j-0003SI-TU; Fri, 15 Jun 2007 18:20:35 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1HzK9i-0003SB-Tf for ltru-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 18:20:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzK9i-0003Rz-Jd for ltru@ietf.org; Fri, 15 Jun 2007 18:20:34 -0400
Received: from 145.nexbyte.net ([62.197.41.145]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzK9h-0001FW-28 for ltru@ietf.org; Fri, 15 Jun 2007 18:20:34 -0400
Received: from DebbieLaptop ([83.67.121.192]) by 145.nexbyte.net with MailEnable ESMTP; Fri, 15 Jun 2007 23:20:30 +0100
From: Debbie Garside <debbie@ictmarketing.co.uk>
To: addison@yahoo-inc.com, 'Randy Presuhn' <randy_presuhn@mindspring.com>
Subject: RE: [Ltru] RE: ISO 639-2 decision: "mis"
Date: Fri, 15 Jun 2007 23:20:22 +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: Aceveff/EbHGDmcCRm6797pzZcEIvQAIRDHQ
In-Reply-To: <4672D81B.4090700@yahoo-inc.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Message-Id: <E1HzK9i-0003SB-Tf@megatron.ietf.org>
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

Just a slight comment:

Addison wrote:

>It SHOULD NOT be used except when 
> other means of identifying the language are not available. 

Double nots are not good :-)

I propose:

"It should only be used when other means of identifying the language are
unavailable."

Debbie
 

> -----Original Message-----
> From: Addison Phillips [mailto:addison@yahoo-inc.com] 
> Sent: 15 June 2007 19:19
> To: Randy Presuhn
> Cc: LTRU Working Group
> Subject: Re: [Ltru] RE: ISO 639-2 decision: "mis"
> 
> Randy Presuhn wrote:
> > 
> > I disagree with the phrase "or when the range of language tags 
> > supported in a given application are constrained."  If the 
> application 
> > knows what language it is, it should use the correct tag, if one 
> > exists.  If the application doesn't know what language is 
> in use, "und" would be correct.
> 
> That's nice in theory. But some applications use a subset of 
> tags (I used the MARC21 example in the text) and then 
> transmit them through another system (where the larger range 
> of RFC 4646 is available). Those systems only know that the 
> content is 'mis' (because it is tagged that
> way) and not what the miscellaneous language happens to be.
> 
> We don't define what subtags applications are capable of 
> supporting or required to support elsewhere. We should focus 
> on providing appropriate guidance (which is not to use the 
> subtag). I note that Peter's use of MAY doesn't reflect the 
> current draft.
> 
> I propose that we modify the draft to say the following. Please note: 
> the paragraph format is consistent with the other items in 
> that section. 
> I think that folks should glance at that text when proposing edits.
> 
> --
> The 'mis' (Uncoded) primary language subtag is used to 
> identify linguistic content whose language is known but 
> cannot otherwise be identified. It is intended for use when 
> the range of language tags is constrained or for languages 
> not otherwise categorized. It SHOULD NOT be used except when 
> other means of identifying the language are not available. 
> For example, a library application might be limited to the 
> set of subtags defined for use by the [MARC21] standard. The 'mis' 
> subtag might be used by this application for languages not 
> included in that set.
> --
> 
> Comments?
> 
> Addison
> 
> --
> Addison Phillips
> Globalization Architect -- Yahoo! Inc.
> Chair -- W3C Internationalization Core WG
> 
> Internationalization is an architecture.
> It is not a feature.
> 
> 
> _______________________________________________
> 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