Re: Why the normative form of IETF Standards is ASCII
Julian Reschke <julian.reschke@gmx.de> Thu, 11 March 2010 17:38 UTC
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 903B43A6BF2 for <ietf@core3.amsl.com>; Thu, 11 Mar 2010 09:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.216
X-Spam-Level:
X-Spam-Status: No, score=-5.216 tagged_above=-999 required=5 tests=[AWL=-2.617, BAYES_00=-2.599]
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 4jMYvQVokvf6 for <ietf@core3.amsl.com>; Thu, 11 Mar 2010 09:38:29 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id D6E7A3A6C53 for <ietf@ietf.org>; Thu, 11 Mar 2010 09:12:37 -0800 (PST)
Received: (qmail invoked by alias); 11 Mar 2010 17:12:39 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.105]) [217.91.35.233] by mail.gmx.net (mp042) with SMTP; 11 Mar 2010 18:12:39 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18JT/QLUh8J575LmLFt6IGdYkKhnXDhIAZWPdMiAU WO+fzwhN0fQkmh
Message-ID: <4B992481.1010401@gmx.de>
Date: Thu, 11 Mar 2010 18:12:33 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Why the normative form of IETF Standards is ASCII
References: <1028365c1003110732o1b2ffa1bmd97cffbb3985dde0@mail.gmail.com> <202705b1003110854j232d8b19ye17075b9c527a34f@mail.gmail.com>
In-Reply-To: <202705b1003110854j232d8b19ye17075b9c527a34f@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.67000000000000004
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 11 Mar 2010 17:38:30 -0000
On 11.03.2010 17:54, Jorge Amodio wrote: > Besides your eyes, (only one in some cases), you don't need any extra > junkware to be able to read the RFCs, even better, without eyes you > still can do it since text to speech works very nicely with ASCII. > ... I'd claim that accessibility for properly authored HTML will actually be better, for instance the markup can express whether something is prose or artwork. Best regards, Julian
- Why the normative form of IETF Standards is ASCII Donald Eastlake
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- RE: Why the normative form of IETF Standards is A… Richard Shockey
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… Mark Atwood
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Huub van Helvoort
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- RE: Why the normative form of IETF Standards is A… Eric Gray
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Henrik Levkowetz
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Donald Eastlake
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… John Levine
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… David Morris
- Re: Why the normative form of IETF Standards is A… Stefan Winter
- Re: Why the normative form of IETF Standards is A… Stefan Winter
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Ingemar Johansson S
- RE: Why the normative form of IETF Standards is A… Dearlove, Christopher (UK)
- Re: Why the normative form of IETF Standards is A… Dave Cridland
- Re: Why the normative form of IETF Standards is A… Arnt Gulbrandsen
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Mark Andrews
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Rich Kulawiec
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… ned+ietf
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Jari Arkko
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Jari Arkko
- Re: Why the normative form of IETF Standards is A… Dave CROCKER
- Re: Why the normative form of IETF Standards is A… Jari Arkko
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Periodic debates Dave CROCKER
- Re: Periodic debates Jorge Amodio
- Re: Periodic debates Dave CROCKER
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Periodic debates Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is A… Lars Eggert
- Re: Why the normative form of IETF Standards is A… John R. Levine
- Re: I-Ds are not RFCs, was Why the normative form… John Levine
- Re: Why the normative form of IETF Standards is A… Tony Hansen
- Re: Why the normative form of IETF Standards is A… Richard Barnes
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Dave Cridland
- Re: Why the normative form of IETF Standards is A… Bob Braden
- Re: Why the normative form of IETF Standards is A… John R. Levine
- Re: Why the normative form of IETF Standards is A… Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Arnt Gulbrandsen
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Marc Petit-Huguenin
- Re: Why the normative form of IETF Standards is A… Tony Finch
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… John Levine
- Re: Why the normative form of IETF Standards is A… John Levine
- Re: Why the normative form of IETF Standards is A… Arnt Gulbrandsen
- Make HTML and PDF more prominent, was: Re: Why th… Iljitsch van Beijnum
- Re: Make HTML and PDF more prominent, was: Re: Wh… Dave Cridland
- Re: Make HTML and PDF more prominent, was: Re: Wh… Masataka Ohta
- Re: Make HTML and PDF more prominent, was: Re: Wh… Ole Jacobsen
- A state of spin ... presented in ASCII (was: Make… SM
- Re: Why the normative form of IETF Standards is A… Henning Schulzrinne
- Re: Make HTML and PDF more prominent, was: Re: Wh… todd glassey
- Re: Make HTML and PDF more prominent, was: Re: Wh… Michael Dillon
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Bob Braden
- Re: Make HTML and PDF more prominent, was: Re: Wh… Iljitsch van Beijnum
- Re: A state of spin ... presented in ASCII todd glassey
- Re: Make HTML and PDF more prominent, was: Re: Wh… Martin Rex
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- Re: Make HTML and PDF more prominent, was: Re: Wh… Peter Saint-Andre
- Re: Make HTML and PDF more prominent, was: Re: Wh… Randy Presuhn
- Re: Make HTML and PDF more prominent, was: Re: Wh… Martin Rex
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Melinda Shore
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: A state of spin ... presented in ASCII SM
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Make HTML and PDF more prominent, was: Re: Wh… Michael Dillon
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Make HTML and PDF more prominent, was: Re: Wh… Michael Dillon
- Re: Make HTML and PDF more prominent, was: Re: Wh… Donald Eastlake
- Re: Make HTML and PDF more prominent, was: Re: Wh… Tim Bray
- Re: A state of spin ... presented in ASCII Michael Dillon
- Re: Make HTML and PDF more prominent, was: Re: Wh… Bob Braden
- Re: Why the normative form of IETF Standards is A… Bob Braden
- Re: Why the normative form of IETF Standards is A… Tony Hansen
- Re: Make HTML and PDF more prominent, was: Re: Wh… Yoav Nir
- Re: Make HTML and PDF more prominent, was: Re: Wh… Yoav Nir
- Re: Make HTML and PDF more prominent, was: Re: Wh… Donald Eastlake
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: A state of spin ... presented in ASCII Doug Ewell
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Make HTML and PDF more prominent, was: Re: Wh… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Periodic debates Sean Turner
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: A state of spin ... presented in ASCII Doug Ewell
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- RE: A state of spin ... presented in ASCII Wes Beebee (wbeebee)
- Re: Make HTML and PDF more prominent, was: Re: Wh… Dave Cridland
- Re: A state of spin ... presented in ASCII Phillip Hallam-Baker
- Re: Make HTML and PDF more prominent, was: Re: Wh… Martin Rex
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Using xml2rfc (was: Re: Why the normative form of… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Using xml2rfc (was: Re: Why the normative for… Fred Baker
- Re: Why the normative form of IETF Standards is A… Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- NroffEdit updated with December 2009 boilerplate Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Yoav Nir
- Re: Why the normative form of IETF Standards is A… Bill Fenner
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Stefan Santesson