Re: New Non-WG Mailing List: IETF-822
John C Klensin <john-ietf@jck.com> Fri, 15 June 2012 21:21 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0A311E80E1 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:21:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level:
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IlK-EHTzpEd for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:21:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C613B11E8088 for <ietf@ietf.org>; Fri, 15 Jun 2012 14:21:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Sfdqn-000Ntn-Eu; Fri, 15 Jun 2012 17:14:37 -0400
Date: Fri, 15 Jun 2012 17:20:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@iecc.com>, ietf@ietf.org
Subject: Re: New Non-WG Mailing List: IETF-822
Message-ID: <60F818CB9BBA86B709B1E1D2@JcK-HP8200.jck.com>
In-Reply-To: <20120615195854.71801.qmail@joyce.lan>
References: <20120615195854.71801.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:21:10 -0000
--On Friday, June 15, 2012 19:58 +0000 John Levine <johnl@iecc.com> wrote: >> Maybe, in the interest of interplanetaryization (i19n ?) and >> multigalacticism (m13m ?) we should start using FoPSCII and >> Galicode references in our documents and noting that ASCII and >> Unicode are temporary substitutes. > > It hardly seems worth the effort, since the only difference > between ASCII and FoPSCII is that the ASCII # is replaced by > the modern currency symbol, and, of course, they put the > little gap back in the vertical bar to resolve the concerns > about religious and cultural insensitivty. Huh? ISO/IEC 646 IRV (another candidate for a FoPSCII precursor) replaces the ASCII $, not #, with that universal currency symbol. As for that vertical bar, sufficiently elderly practitioners of the art of Character Confusion and Coding (CCS) will recall that the ancient Earthling-Based Convention for Difficult Information Coding included two peculiar characters: a mathematical "not" sign that closely resembled Unicode's "⌐" (U+2310) and that broken vertical bar. Those characters spawned multiple wars over how they should be mapped into "ASCII" and "ISO/IEC 646" with one group arguing for caret and (solid) vertical bar, another for tilde and exclamation mark, and a third for exclamation mark and [solid] vertical bar. After much bloodshed, 16 and 32 bit character sets were invented so that almost everyone could contemplate their cakes while eating them and continued dissenters were tortured until they repented. Those battles were repeated in the development of FoPSCII when it was noticed that the 5th character of the Klingon alphabet was confusable with both the not-sign, Greek upper case Gamma, and Latin "r". In addition, the Klingon numeral 8 was easily confused with Cyrillic "Ж". This created a variant problem that the Intergalactic Consortium for Arbitrary Names and Numbers could not dismiss because of some of the advocates had a more effective means of persuasion than merely hiring lawyers. :-( john
- Re: New Non-WG Mailing List: IETF-822 Peter Saint-Andre
- Re: [IETF] Re: New Non-WG Mailing List: IETF-822 Warren Kumari
- Re: [IETF] Re: [IETF] Re: New Non-WG Mailing List… Warren Kumari
- Re: New Non-WG Mailing List: IETF-822 Yoav Nir
- Re: New Non-WG Mailing List: IETF-822 Harald Alvestrand
- Re: New Non-WG Mailing List: IETF-822 Steven Bellovin
- Re: New Non-WG Mailing List: IETF-822 John C Klensin
- Re: New Non-WG Mailing List: IETF-822 John Levine
- Re: New Non-WG Mailing List: IETF-822 Dave Crocker
- Re: New Non-WG Mailing List: IETF-822 John C Klensin
- Re: New Non-WG Mailing List: IETF-822 John R. Levine
- Re: New Non-WG Mailing List: IETF-822 James Polk
- Re: New Non-WG Mailing List: IETF-822 Noel Chiappa