[Ltru] Re: Language tags in the future version of HTTP
"Frank Ellermann" <nobody@xyzzy.claranet.de> Sat, 01 December 2007 22:21 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 1IyaiM-0004N2-RI; Sat, 01 Dec 2007 17:21:34 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IyaiM-0004Mm-8V for ltru-confirm+ok@megatron.ietf.org; Sat, 01 Dec 2007 17:21:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyaiL-0004Ld-Uh for ltru@lists.ietf.org; Sat, 01 Dec 2007 17:21:33 -0500
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IyaiF-00075w-CY for ltru@lists.ietf.org; Sat, 01 Dec 2007 17:21:33 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Iyai6-00015N-5S for ltru@lists.ietf.org; Sat, 01 Dec 2007 22:21:18 +0000
Received: from c-180-160-112.hh.dial.de.ignite.net ([62.180.160.112]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Sat, 01 Dec 2007 22:21:18 +0000
Received: from nobody by c-180-160-112.hh.dial.de.ignite.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Sat, 01 Dec 2007 22:21:18 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ltru@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 01 Dec 2007 23:23:12 +0100
Organization: <http://purl.net/xyzzy>
Lines: 59
Message-ID: <fismog$2qe$1@ger.gmane.org>
References: <E1IyTGd-0001uH-V7@megatron.ietf.org> <006d01c83442$02855ec0$6601a8c0@DGBP7M81>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: c-180-160-112.hh.dial.de.ignite.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc:
Subject: [Ltru] Re: Language tags in the future version of HTTP
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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
Doug Ewell wrote: >> For 2616bis they could use a simplified syntax in the direction >> of tag = primary *( "-" auxiliary ) directly expanded >> in tag = 1*8( ALPHA / DIGIT ) *( "-" 1*8( ALPHA / DIGIT )) with >> a note in prose that tags are actually supposed to be BCP 47 tags. > We tried that with the "grandfathered" production in 4646, and > we got complaints from people unhappy with the loose syntax that > appeared, taken out of context, to allow "en-a-b-c-d-e". 2616bis (http) mainly needs to *_transport_* tags, interpreting them is IMO not the same layer. We likely agree that 2616bis "MUST NOT" copy 4646 syntax, especially not while 4646bis rewrites major parts of it. They could try tag = <as specified in BCP 47> adding some valid examples based on the current registry. It's already clear that they get rid of any 1*8( ALPHA ), and i-cherokee or en-cockney in the latest 2616bis draft were also bad ideas. > Now we have a separate "irregular" production that enumerates all > the grandfathered tags that don't fit the rest of the syntax. That list could be trimmed by regulating i-whatever instead of the zero registered languages matching 5*8( ALPHA ) for i-uniling or i-liaden. If a registered language ever needs scripts, or other subtags, then it most likely already qualifies for a proper 639-3 code. My crystal ball says, hard to judge based on no real case. > are we going to remove the extlang production from the syntax > and add a lot more items to the "irregular" list I'd hope that we do this. We could mitigate it by building some sublists, e.g. sgn-irregular / zh-irregular / other-irregular > If their home-grown syntax doesn't agree with BCP 47, it's not > clear which one people will believe. Well, the generic URI syntax in STD 66 doesn't explain details for various specific URI schemes, including schemes specified in STD 66. Nothing's wrong with that, just a different level of abstraction. If you want to know how many servers handle the name=value details of queries you're forced to test it with real servers, it's not specified in STD 66. If you want to know how mailto URIs work (if at all) you have to look in Martin's draft, and after that you've to judge how far away the I-D still is from anything related to real mailto-URIs. But real mailto-URIs not matching the generic STD 66 syntax are broken, if they work or not, so it's not quite hopeless... :-) > Remember how many people thought RFC 1766 and 3066 promised > only "xx" and "xx-XX". Yes, but it wasn't too hard to learn that this wasn't the case, with beautiful examples such as i-default or en-GB-oed. If an implementor doesn't bother to read the spec. trying to improve the spec. might be a waste of time (unless it's an improvement towards readability and KISS) Frank _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] John Cowan throws in the towel on extlangs John Cowan
- [Ltru] Fallback vs. Macrolanguage? (was: John Cow… Addison Phillips
- RE: [Ltru] Fallback vs. Macrolanguage? (was: John… Don Osborn
- [Ltru] Re: John Cowan throws in the towel on extl… John Cowan
- RE: [Ltru] John Cowan throws in the towel on extl… Peter Constable
- RE: [Ltru] John Cowan throws in the towel on extl… Don Osborn
- Re: [Ltru] John Cowan throws in the towel on extl… John Cowan
- Re: [Ltru] John Cowan throws in the towel on extl… Addison Phillips
- [Ltru] Re: Fallback vs. Macrolanguage? (was: John… John Cowan
- [Ltru] Re: John Cowan throws in the towel on extl… Doug Ewell
- [Ltru] Re: John Cowan throws in the towel on extl… Doug Ewell
- RE: [Ltru] John Cowan throws in the towel on extl… Peter Constable
- RE: [Ltru] John Cowan throws in the towel on extl… Karen_Broome
- Re: [Ltru] John Cowan throws in the towel on extl… John Cowan
- [Ltru] Re: John Cowan throws in the towel on extl… Frank Ellermann
- [Ltru] Re: John Cowan throws in the towel on extl… Doug Ewell
- [Ltru] Re: Language tags in the future version of… Doug Ewell
- [Ltru] RFC 1591 (was: Re: draft-ietf-ltru-4646bis… Doug Ewell
- Re: [Ltru] Re: John Cowan throws in the towel on … Addison Phillips
- RE: [Ltru] Re: John Cowan throws in the towel on … Peter Constable
- RE: [Ltru] Re: Language tags in the future versio… Peter Constable
- [Ltru] Re: John Cowan throws in the towel on extl… Doug Ewell
- [Ltru] Re: Language tags in the future version of… Frank Ellermann
- [Ltru] Re: John Cowan throws in the towel on extl… Frank Ellermann
- Re: [Ltru] Re: John Cowan throws in the towel on … Addison Phillips
- [Ltru] Re: RFC 1591 Frank Ellermann
- [Ltru] Re: Re: John Cowan throws in the towel on … Frank Ellermann
- Re: [Ltru] RFC 1591 (was: Re: draft-ietf-ltru-464… John Cowan
- [Ltru] Re: John Cowan throws in the towel on extl… Doug Ewell
- RE: [Ltru] RFC 1591 (was: Re: draft-ietf-ltru-464… Debbie Garside
- [Ltru] Re: John Cowan throws in the towel on extl… John Cowan
- Re: [Ltru] Re: John Cowan throws in the towel on … Karen_Broome
- Re: [Ltru] Re: John Cowan throws in the towel on … John Cowan
- RE: [Ltru] Re: John Cowan throws in the towel on … Peter Constable