IETF Logo Mail Archive

Re: [Ltru] Re: Registry change of the day: prefix with more than onesubtag

"Randy Presuhn" <randy_presuhn@mindspring.com> Sun, 15 July 2007 00:16 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 1I9rmu-0000P3-Lm; Sat, 14 Jul 2007 20:16:36 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I9rmt-0000Ot-OV for ltru-confirm+ok@megatron.ietf.org; Sat, 14 Jul 2007 20:16:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9rmt-0000Ol-El for ltru@ietf.org; Sat, 14 Jul 2007 20:16:35 -0400
Received: from elasmtp-curtail.atl.sa.earthlink.net ([209.86.89.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9rmp-0000Gj-3H for ltru@ietf.org; Sat, 14 Jul 2007 20:16:35 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=NPKQBgp3x/X2C/devrLF60z8gLQTPEcE56wRwE6jQBYMDQ2PYKuJqvbZ0xqUHN+4; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.82.234] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1I9rmo-0000Fe-9w for ltru@ietf.org; Sat, 14 Jul 2007 20:16:30 -0400
Message-ID: <000e01c7c675$82d4b5c0$6601a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: LTRU Working Group <ltru@ietf.org>
References: <E1I9NZU-0007Ot-8H@megatron.ietf.org> <00fe01c7c660$92e59cf0$6401a8c0@DGBP7M81>
Subject: Re: [Ltru] Re: Registry change of the day: prefix with more than onesubtag
Date: Sat, 14 Jul 2007 17:17:19 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888fa44b31bb60a935681c0f3e9ceae2ce07612036de8b91687350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.82.234
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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

Hi -

As a technical contributor.

> From: "Doug Ewell" <dewell@roadrunner.com>
> To: "LTRU Working Group" <ltru@ietf.org>
> Sent: Saturday, July 14, 2007 2:47 PM
> Subject: [Ltru] Re: Registry change of the day: prefix with more than onesubtag
...
> My question was what a piece of software should do.  Software is 
> notoriously bad at applying wisdom to situations like this.
...

Two cases:
   when receiving a "stupid" tag, I don't think there's any requirement for
   software to recognize it as stupid, nor to process it in any special way

   when we consider the case of software putting a tag on something, I very
   much doubt that the software is creating these things "generatively".
   Rather, there is some set of language / region / orthography etc. combinations
   the software knows about, and for each of these it knows what the tag is.
   The question of whether a tag would be stupid doesn't arise; it had to be
   addressed when the set of languages supported was specified.

Randy



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

v2.29.0 | Report a Bug | By Email | System Status