RE: [Ltru] Updated draft-4646bis...
"David Dalby" <daviddalby@linguasphere.info> Wed, 01 August 2007 20:22 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 1IGKiB-0005Ca-6D; Wed, 01 Aug 2007 16:22:27 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IGKi9-0005CO-Ay for ltru-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 16:22:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGKi9-0005CG-14 for ltru@ietf.org; Wed, 01 Aug 2007 16:22:25 -0400
Received: from customermail2.easily.co.uk ([212.53.64.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGKi6-00010y-Uk for ltru@ietf.org; Wed, 01 Aug 2007 16:22:24 -0400
Received: from [86.132.150.255] (account ya7to240sqpm HELO Laptop) by customermail2.easily.co.uk (CommuniGate Pro SMTP 4.1.8) with ESMTP id 109992662; Wed, 01 Aug 2007 21:22:19 +0100
From: David Dalby <daviddalby@linguasphere.info>
To: 'Addison Phillips' <addison@yahoo-inc.com>
Subject: RE: [Ltru] Updated draft-4646bis...
Date: Wed, 01 Aug 2007 21:22:19 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcfUVWVJlv5taHzxTs2eWUfDlUPCUwAIxMFg
In-Reply-To: <46B0AC1B.60702@yahoo-inc.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Message-ID: <auto-000109992662@customermail2.easily.co.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e233469409eae36784776b094a259e13
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>
Content-Type: multipart/mixed; boundary="===============2016907536=="
Errors-To: ltru-bounces@ietf.org
Addison, You seem to have missed the second in my quick sequence of two e-mails. What is wrong with the simple statement (?): "A langtag may be formally valid but remain unrealized in meaning, e.g. ...." This even allows for the unlikely event of its meaning becoming realized. Of course, the large majority of ALL potential langtags with subtags will never be realized in meaning, but this very obvious point should surely be dealt with as briefly as possible. Regards, David -----Original Message----- From: Addison Phillips [mailto:addison@yahoo-inc.com] Sent: 01 August 2007 16:52 To: David Dalby Cc: debbie@ictmarketing.co.uk; 'Marion Gunn'; 'LTRU Working Group' Subject: Re: [Ltru] Updated draft-4646bis... You have to read the document. The terms "valid" and "well-formed" have a different meaning in the context of RFC 4646/4646bis. The term "valid" was chosen carefully in this context. Mark and others are correct that every tag has *a* meaning (we even spell out the one for the "meaningless" tag in the example). But that does not mean that every tag is *meaningful*. How about this version instead: <t>Validity of a tag is not everything. While every valid tag has a meaning, it might not represent any real language usage. This is unavoidable in a system in which subtags can be combined freely. For example, tags such as "ar-Cyrl-CO" (Arabic, Cyrillic script, as used in Colombia ) or "tlh-Kore-AQ-fonipa" (Klingon, Korean script, as used in Antarctica, IPA phonetic transcription) are both valid and unlikely to represent a useful combination of language attributes.</t> Addison David Dalby wrote: > I agree! > > David > > _____________________________________________________ > > Dr David Dalby > The Linguasphere Observatory > Hebron > Whitland > Wales > SA34 0XT > > -----Original Message----- > From: Debbie Garside [mailto:debbie@ictmarketing.co.uk] > Sent: 01 August 2007 13:44 > To: addison@yahoo-inc.com; 'Marion Gunn' > Cc: 'LTRU Working Group' > Subject: RE: [Ltru] Updated draft-4646bis... > > Addison wrote: > >> A tag can be valid yet meaningless. > > I don't really like this as it seems, on the face of it, a contradiction in > terms. I would propose one of the following: > > --- > A tag can be well formed yet meaningless. > > A tag can be well formed in terms of syntax, and thus valid, yet meaningless > in terms of its attributes. For example, ... > > --- > > Best > > Debbie > >> -----Original Message----- >> From: Addison Phillips [mailto:addison@yahoo-inc.com] >> Sent: 31 July 2007 16:52 >> To: Marion Gunn >> Cc: LTRU Working Group >> Subject: Re: [Ltru] Updated draft-4646bis... >> >> Marion Gunn wrote: >> > >> > However, here goes with one more attempt: >> > >> > "For example, although a tag such as 'ar-Cyrl-CO' (Arabic, >> as used in > Columbia, > written in Cyrillic script) is >> valid, it is [most] unlikely to be of > use, because > such >> combination of attributes is unlikely to occur in actual >> language > use." >> > >> >> I note that it is useful to look at the actual editor's copy >> when suggesting minor editorial changes. Upon reflection, I >> found the current sentence to be a bit of a run-on. I've >> taken your suggestion of 'unlikely' and edited further such >> that the paragraph now reads: >> >> <t>Validity of a tag is not everything. A tag can be valid >> yet meaningless. This is unavoidable with a generative system >> like the language subtag mechanism. For example, a tag such >> as "ar-Cyrl-CO" >> (Arabic, Cyrillic script, as used in Colombia) is perfectly valid. >> However, it is unlikely to be a useful tag, as it represents >> an unlikely combination of language attributes that is >> probably unrelated to any real language usage.</t> >> >> After five minutes from now, you will need to comment on >> draft-08. I'm always happy to consider editorial changes that >> improve the text. >> >> 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 > > -- 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] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Mark Davis
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Mark Davis
- [Ltru] Re: Updated draft-4646bis... Doug Ewell
- Re: [Ltru] Re: Updated draft-4646bis... Addison Phillips
- RE: [Ltru] Updated draft-4646bis... Peter Constable
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Martin Duerst
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- RE: [Ltru] Updated draft-4646bis... Peter Constable
- RE: [Ltru] Updated draft-4646bis... Peter Constable
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Randy Presuhn
- RE: [Ltru] Updated draft-4646bis... Debbie Garside
- Re: [Ltru] Updated draft-4646bis... Marion Gunn
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Marion Gunn
- Re: [Ltru] Updated draft-4646bis... Mark Davis
- Re: [Ltru] Updated draft-4646bis... Marion Gunn
- Re: [Ltru] Updated draft-4646bis... Marion Gunn
- RE: [Ltru] Updated draft-4646bis... David Dalby
- RE: [Ltru] Updated draft-4646bis... David Dalby
- [Ltru] The third level of conformance (Was: Updat… Stephane Bortzmeyer
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Mark Davis
- RE: [Ltru] Updated draft-4646bis... David Dalby
- RE: [Ltru] Updated draft-4646bis... Debbie Garside
- Re: [Ltru] Updated draft-4646bis... Mark Davis
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Updated draft-4646bis... Addison Phillips
- RE: [Ltru] Updated draft-4646bis... Debbie Garside
- RE: [Ltru] Updated draft-4646bis... David Dalby
- [Ltru] Re: Updated draft-4646bis... Stephane Bortzmeyer
- [Ltru] Re: Updated draft-4646bis... Doug Ewell
- [Ltru] Re: Updated draft-4646bis... Addison Phillips
- Re: [Ltru] Re: Updated draft-4646bis... Addison Phillips
- RE: [Ltru] Updated draft-4646bis... Peter Constable
- RE: [Ltru] Updated draft-4646bis... Peter Constable
- [Ltru] Re: Updated draft-4646bis... Doug Ewell
- Re: [Ltru] Re: Updated draft-4646bis... Addison Phillips
- RE: [Ltru] Re: Updated draft-4646bis... Peter Constable
- [Ltru] Question on variants Karen_Broome
- [Ltru] Serbo-Croatian Deprecations and Variants Karen_Broome
- Re: [Ltru] Serbo-Croatian Deprecations and Varian… Addison Phillips