Re: [Ltru] Proposed resolution for Issue 13 (language tags)

Martin Duerst <duerst@it.aoyama.ac.jp> Wed, 16 April 2008 07:39 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3BF83A6C98; Wed, 16 Apr 2008 00:39:01 -0700 (PDT)
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A7043A6D12 for <ltru@core3.amsl.com>; Wed, 16 Apr 2008 00:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.034
X-Spam-Level: **
X-Spam-Status: No, score=2.034 tagged_above=-999 required=5 tests=[AWL=-1.172, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_23=0.6, RCVD_IN_NJABL_RELAY=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tjUzzfF9Hu5q for <ltru@core3.amsl.com>; Wed, 16 Apr 2008 00:38:59 -0700 (PDT)
Received: from scmailgw1.scop.aoyama.ac.jp (scmailgw1.scop.aoyama.ac.jp [133.2.251.194]) by core3.amsl.com (Postfix) with ESMTP id AF39C3A6C98 for <ltru@ietf.org>; Wed, 16 Apr 2008 00:38:53 -0700 (PDT)
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id m3G7dPib014381 for <ltru@ietf.org>; Wed, 16 Apr 2008 16:39:27 +0900 (JST)
Received: from (133.2.206.133) by scmse1.scbb.aoyama.ac.jp via smtp id 7134_3cbde102_0b88_11dd_96e0_0014221fa3c9; Wed, 16 Apr 2008 16:39:24 +0900
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:44343) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S5D8068> for <ltru@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 16 Apr 2008 16:34:37 +0900
Message-Id: <6.0.0.20.2.20080416155918.08629ec0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Wed, 16 Apr 2008 16:01:32 +0900
To: Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>, LTRU Working Group <ltru@ietf.org>
From: Martin Duerst <duerst@it.aoyama.ac.jp>
In-Reply-To: <48049274.3090501@gmx.de>
References: <48037FF9.9030103@gmx.de> <48049274.3090501@gmx.de>
Mime-Version: 1.0
Subject: Re: [Ltru] Proposed resolution for Issue 13 (language tags)
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

At 20:33 08/04/15, Julian Reschke wrote:
>
>OK,
>
>thanks for all the feedback so far. I (hopefully) have addressed many of the issues; here's the new proposed text for 3.5:
>
>------
>3.5.  Language Tags
>
>    A language tag, as defined in [RFC4646], identifies a natural
>    language spoken, written, or otherwise conveyed by human beings for
>    communication of information to other human beings.  Computer
>    languages are explicitly excluded.  HTTP uses language tags within
>    the Accept-Language and Content-Language fields.
>
>    In summary, a language tag is composed of one or more parts: A
>    primary language tag and a possibly empty series of subtags:
>
>      language-tag  = <Language-Tag, defined in [RFC4646], Section 2.1>
>
>    White space is not allowed within the tag and all tags are case-
>    insensitive.  The name space of language subtags is administered by
>    the IANA (see
>    <http://www.iana.org/assignments/language-subtag-registry>).

This is going very much in the right direction, but there
is some confusion about what a subtag means. Where it says
"A primary language tag and a possibly empty series of subtags",
the first tag (e.g. 'en' in 'en-US') seems to not be a subtag,
but the subtag registry clearly also includes that as a subtag,
and RFC 4646 is using terminology consistent with that.

Regards,   Martin.

>    Example tags include:
>
>      en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
>
>    See RFC 4646 for further information.
>------
>
>(see also <http://www.tools.ietf.org/wg/httpbis/trac/ticket/13>).
>
>
>BR, Julian
>


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     

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