Re: [irsg] Resending: Page numbers in RFCs questions / preferences

Toerless Eckert <tte@cs.fau.de> Mon, 26 October 2020 15:02 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D407F3A0C0A for <wgchairs@ietfa.amsl.com>; Mon, 26 Oct 2020 08:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_L-TfO4NPvH for <wgchairs@ietfa.amsl.com>; Mon, 26 Oct 2020 08:02:47 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98CD73A0C16 for <wgchairs@ietf.org>; Mon, 26 Oct 2020 08:02:46 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 062C254843F; Mon, 26 Oct 2020 16:02:42 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id F322F440059; Mon, 26 Oct 2020 16:02:41 +0100 (CET)
Date: Mon, 26 Oct 2020 16:02:41 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: David Noveck <davenoveck@gmail.com>, WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
Subject: Re: [irsg] Resending: Page numbers in RFCs questions / preferences
Message-ID: <20201026150241.GK48111@faui48f.informatik.uni-erlangen.de>
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.com> <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/z7tlrFhMS_UOGa2CAuxAJ-h-m8s>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 15:02:50 -0000

Is there any reason why the tools team would not be able to produce
a rendered version that does incude page numbers ? PDF and txt ?
Call it RFC classic format ?

This is even just for simple examination like checking how long
a particular RFC is. Ridiculous if there is no indication of that.

If so, does a request like that first need to go into some RFC,
or just into the infinite wish list of the tools team where it might
only be prioritized by rallying up the community to provide some
+1 (in whatever fashion is appropriate - which i am unclear about...).

Cheers
    Toerless

On Mon, Oct 26, 2020 at 01:55:40PM +0100, Carsten Bormann wrote:
> On 2020-10-26, at 11:51, David Noveck <davenoveck@gmail.com> wrote:
> > 
> > I think it happened with the conversion to v3 xml.  At that time, the 72-character-ragged-right .txt format ceased to be considered canonical (long overdue in my opinion).  As a result, in accord with some RFC that I was pointed to, a decision was made (by whom it wasn't clear) to make all TOCs the same, so that the pdf and text TOCs lost theirs since there was no way to add them to html which doesn't have them.  The logic is impeccable if you grant the premises and nobody ever considered rethinking the premises when it resulted in nearly useless printed documents. Sigh!
> 
> Obviously, with canonical XML, there is no good solution to this problem: Different renditions will have different concepts of pages, so the TOC???s won???t align.
> 
> (That is not a good argument for then finally choosing what is probably the worst possible solution to this problem.  I think what happened is that nobody thought about PDF where we continue to have pages, so there never really was a problem specific to retaining pages and thus page numbers in the TXT.)
> 
> Grüße, Carsten

-- 
---
tte@cs.fau.de