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

"Mark Davis" <mark.davis@icu-project.org> Wed, 16 April 2008 15:58 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 9751828C255; Wed, 16 Apr 2008 08:58:10 -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 F38763A6C92 for <ltru@core3.amsl.com>; Wed, 16 Apr 2008 08:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level:
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6]
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 KN3q+oqDPVxc for <ltru@core3.amsl.com>; Wed, 16 Apr 2008 08:58:08 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by core3.amsl.com (Postfix) with ESMTP id 3D01528C255 for <ltru@ietf.org>; Wed, 16 Apr 2008 08:58:07 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 2so1255905ywt.49 for <ltru@ietf.org>; Wed, 16 Apr 2008 08:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=zdarWrWjRMAs21/iv7moyui8LJXtB7UqnosNqNXf8rc=; b=m8fs9OFyquGinM9QlTPae1Q21UHCBbwX4i9MKtgSZllAvaiBQvXwEBP1U8eS9rKYXF0wfCinnnskxu7/tItGHCTMeRFjJSG0aq+dlgFEGDt49NPQly2m7Fsu2FWF7nx4QnKQNuK1xCEojHHvW2AMJkkZG4YXFxxLCRLm644O4AA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=flOM4KCw3xqq3ViDL1gnhXisAc3XTx8SOCF/hHrLjVDP6KqMHY1RmyBa3WS442cOWjKPckkS7zuFRbzCG0H7bwpDzQKUIMaQQre6gmp8ZkwJN8pMCd4bZVroPqWhw6nd4o1IKcmmUFFfMfAvRr3i9VHibhvwnpM1mbWjUCuyacM=
Received: by 10.150.150.3 with SMTP id x3mr319284ybd.93.1208361514430; Wed, 16 Apr 2008 08:58:34 -0700 (PDT)
Received: by 10.150.229.9 with HTTP; Wed, 16 Apr 2008 08:58:34 -0700 (PDT)
Message-ID: <30b660a20804160858k29f835a9w2a90d0ed399fe791@mail.gmail.com>
Date: Wed, 16 Apr 2008 08:58:34 -0700
From: "Mark Davis" <mark.davis@icu-project.org>
To: "Phillips, Addison" <addison@amazon.com>
In-Reply-To: <4D25F22093241741BC1D0EEBC2DBB1DA01200D8D49@EX-SEA5-D.ant.amazon.com>
MIME-Version: 1.0
References: <48037FF9.9030103@gmx.de> <48049274.3090501@gmx.de> <6.0.0.20.2.20080416155918.08629ec0@localhost> <30b660a20804160646n14a12f71r589d1728c72db695@mail.gmail.com> <4D25F22093241741BC1D0EEBC2DBB1DA01200D8D49@EX-SEA5-D.ant.amazon.com>
X-Google-Sender-Auth: aaea4d4c20bb8047
Cc: Julian Reschke <julian.reschke@gmx.de>, LTRU Working Group <ltru@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
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: multipart/mixed; boundary="===============1516569977=="
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

That works for me.

On Wed, Apr 16, 2008 at 8:00 AM, Phillips, Addison <addison@amazon.com>
wrote:

>  Mark wrote:
>
> --
>
> In summary, a language tag is composed of one or more parts: typically a
> primary language subtag followed optionally by a series of other subtags
> such as script and region.
>
> --
>
> I think that is either too specific or not specific enough J
>
>
>
> Perhaps:
>
>
>
> In summary, a language tag is composed of one or more subtags separated by
> hyphens. Typically there will be a primary language subtag to which other
> subtags are sometimes appended to indicate linguistic variations such as
> script or region.
>
>
>
> Addison Phillips
>
> Globalization Architect -- Lab126 (Amazon)
>
> Chair -- W3C Internationalization Core WG
>
>
>
> Internationalization is not a feature.
>
> It is an architecture.
>
>
>
> *From:* ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] *On Behalf Of
> *Mark Davis
> *Sent:* mercredi 16 avril 2008 06:46
> *To:* Martin Duerst
> *Cc:* Julian Reschke; LTRU Working Group; HTTP Working Group
> *Subject:* Re: [Ltru] Proposed resolution for Issue 13 (language tags)
>
>
>
> Agreed. Even that is incorrect, since there may not be a primary language
> subtag, such as in the case of "x-duerst". So I'd recommend something more
> like:
>
> >    In summary, a language tag is composed of one or more parts: A
> >    primary language tag and a possibly empty series of subtags:
> =>
> In summary, a language tag is composed of one or more parts: typically a
> primary language subtag followed optionally by a series of other subtags
> such as script and region.
>
> On Wed, Apr 16, 2008 at 12:01 AM, Martin Duerst <duerst@it.aoyama.ac.jp>
> wrote:
>
> 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
>
>
>
>
> --
> Mark
>



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