IETF Logo Mail Archive

Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?

"John R. Levine" <johnl@iecc.com> Sun, 08 November 2020 17:18 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F8C3A0DA1; Sun, 8 Nov 2020 09:18:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=iecc.com
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 f4z0p5thNrEf; Sun, 8 Nov 2020 09:18:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E82F23A0D9D; Sun, 8 Nov 2020 09:18:34 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AA285F40706; Sun, 8 Nov 2020 09:18:32 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 883DCF40706 for <rfc-interest@rfc-editor.org>; Sun, 8 Nov 2020 09:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H83OAch3y_hF for <rfc-interest@rfc-editor.org>; Sun, 8 Nov 2020 09:18:27 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) by rfc-editor.org (Postfix) with ESMTPS id CD2E9F406F5 for <rfc-interest@rfc-editor.org>; Sun, 8 Nov 2020 09:18:26 -0800 (PST)
Received: (qmail 46807 invoked from network); 8 Nov 2020 17:18:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=b6d2.5fa82862.k2011; i=johnl-iecc.com@submit.iecc.com; bh=o/os8BkdemEPclwLbORBwsCtVWozIAEBkFreGiQRbLA=; b=oPIBg3L53FMh3r2xz0y2QCBxeAcREWHYnUr6bY5KqjW8kQTiLn/NBzJh1P0jfF1hZvNnE6Xb04g8uV9WxAAZigIcfv4Zg0jrsRWFGEkHoODlWWC7YZXBKGoqWhu2q+lXwoe9AAkczv6s85gIBQa7ZJqcnIy5LlrJIIT8CwRoGg2FWi2hrV6YBM17tjkgTj/Jdd/yk0NwvNfZxP6U2if+0zBjMzYC0cWLJT+sJxjgdNOm47JKpD79siJnKBiZObOjPb++U67UZLZ6iaFaGiud4mJgBvTME4Wrrx1a1UlKlRNoSdlpFWlYsFHYQKGn/1ppxKqaHvz1RSe8SMj0Y6mGdQ==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 08 Nov 2020 17:18:25 -0000
Date: Sun, 08 Nov 2020 12:18:25 -0500
Message-ID: <e9e79b9-8829-139-8ec2-50514a44a3e6@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Tony Finch <dot@dotat.at>, Phillip Hallam-Baker <phill@hallambaker.com>
In-Reply-To: <alpine.DEB.2.20.2011081547020.20609@grey.csi.cam.ac.uk>
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <CADaq8jdSeTDWy_0fCV25ykxKFMV1ZBtUMMNesoOuaXCzFVfpOA@mail.gmail.com> <D2D0455D-8D6C-4A19-ACAE-4DD972D83DC1@bluepopcorn.net> <20201028164053.GB12700@faui48f.informatik.uni-erlangen.de> <263C265C19B24BA97AF48934@PSB> <225062D7-C061-4543-8665-53A4F4831510@isc.org> <20201029005519.GT39170@kduck.mit.edu> <A05242FC-C38C-474F-A2AC-412329CA5C52@isc.org> <CAKq15ve-kAFZWH_f7=1XXC5PfxvO-sAzppB1fVTyqUufLftkVg@mail.gmail.com> <D2DB703DBF2A44A19B8F80DD@PSB> <CAKq15vdFVkG6_grNtqUqq-yDwj9QQcHJFZB5+RB-8fdxQXhFSw@mail.gmail.com> <fa36e919-b1a0-5b3c-9b42-54c6fdaadfb@iecc.com> <e8554ea2-1849-279f-733d-5798de8817b9@gmail.com> <26d1ff54-777f-884b-e35-d91e9fe59662@iecc.com> <alpine.DEB.2.20.2011052234320.20609@grey.csi.cam.ac.uk> <CAMm+LwiQtPcNgA3QkyvvaiAwrp0McHaXhsveHmof2XxhKO5ymA@mail.gmail.com> <alpine.DEB.2.20.2011081547020.20609@grey.csi.cam.ac.uk>
MIME-Version: 1.0
Subject: Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

>> The paragraphs are already numbered. All it would take is a small change to
>> the HTML-izer.
>
> A reader needs to know how to refer to specific text regardless of the
> format of the RFC: if paragraph numbers are going to be helpful they need
> to appear in every format with a consistent syntax that's convenient to
> use in things like document reviews.

I see where you're coming from, but I have to push back.  Different 
formats serve different purposes.  It would be technically easy to put 
paragraph numbers in the rendered text or PDF, but it would also be ugly 
and cluttered.  We do put thenm in the HTML because they're hidden until 
you hover over the mark at the end of the paragraph.

This comes back around to the question of variant not-quite-the-same 
renderings.  We currently have text without para or page numbers.  Add 
optioons for both and now we have four variant renderings.  I'm not 
unalterably opposed to that, and at least paragraph numbers unlike page 
nunbers should be stable if they appear at all, but I'd really like to 
have a strategy rather than looking at one wart at a time.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email