RE: [Ltru] Re: Updated draft-4646bis...

Peter Constable <petercon@microsoft.com> Fri, 03 August 2007 15:03 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 1IGyh5-0004ak-OZ; Fri, 03 Aug 2007 11:03:59 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IGyh4-0004ae-Qf for ltru-confirm+ok@megatron.ietf.org; Fri, 03 Aug 2007 11:03:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGyh4-0004aW-Fy for ltru@ietf.org; Fri, 03 Aug 2007 11:03:58 -0400
Received: from maila.microsoft.com ([131.107.115.212] helo=smtp.microsoft.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGyh4-0005c4-2d for ltru@ietf.org; Fri, 03 Aug 2007 11:03:58 -0400
Received: from tk1-exhub-c102.redmond.corp.microsoft.com (157.56.116.113) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.0.700.0; Fri, 3 Aug 2007 08:03:57 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.46]) by tk1-exhub-c102.redmond.corp.microsoft.com ([157.56.116.113]) with mapi; Fri, 3 Aug 2007 08:03:56 -0700
From: Peter Constable <petercon@microsoft.com>
To: LTRU Working Group <ltru@ietf.org>
Date: Fri, 03 Aug 2007 08:03:55 -0700
Subject: RE: [Ltru] Re: Updated draft-4646bis...
Thread-Topic: [Ltru] Re: Updated draft-4646bis...
Thread-Index: AcfV3C3hKVCcvorHTFy3cYkP/VOK2QAApIWA
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB83579561A95A97DA@NA-EXMSG-C117.redmond.corp.microsoft.com>
References: <E1IGxTg-0004Jb-8X@megatron.ietf.org> <007b01c7d5d6$5a871bb0$6a01a8c0@DGBP7M81> <46B33E12.4070108@yahoo-inc.com>
In-Reply-To: <46B33E12.4070108@yahoo-inc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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

Arabic as used in Colombia written in Cyrillic is not an absurdity. It's perfectly reasonable; it just doesn't happen to be real.

But you do already have an absurdity: IPA transcription in Korean script: by definition, IPA must be in Latin script. (That's different from phonetic transcription in Korean script, which does exist, BTW.)

In your Klingon and Basque examples, the particular languages, script or regions used do not contribute to the absurdity, though some might wrongly perceive that to be the case. It is only the combination of fonupa with Cyrl that is absurd.


Peter


> -----Original Message-----
> From: Addison Phillips [mailto:addison@yahoo-inc.com]
> Sent: Friday, August 03, 2007 7:39 AM
> To: Doug Ewell
> Cc: LTRU Working Group
> Subject: Re: [Ltru] Re: Updated draft-4646bis...
>
> Doug mentioned:
>  > The passage is supposed to be
>  > about semantically consistent tags that refer to non-existent
> language
>  > variations.
>
> I'm not sure that it is. The section is about "valid-yet-useless" tags,
> which includes, I assume, absurdities. I didn't want to create an
> absurdity by ignoring Prefix. Thus the "problem" (if you can call it
> that) is a dearth of generic variants.
>
> We could use "tlh-Cyrl-AQ-fonupa", I suppose, or maybe
> "eu-Cyrl-SN-fonupa" (Basque, Cyrillic, Senegal, UPA transcription).
>
> 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