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

John C Klensin <john-ietf@jck.com> Tue, 27 October 2020 01:53 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 E52E13A11B7; Mon, 26 Oct 2020 18:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 TIhQeqG_od86; Mon, 26 Oct 2020 18:53:20 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C3AA3A11B6; Mon, 26 Oct 2020 18:53:20 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kXEAn-0003OW-Ix; Mon, 26 Oct 2020 21:53:17 -0400
Date: Mon, 26 Oct 2020 21:53:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ronald Tse <tse@ribose.com>
cc: wgchairs@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>, rsoc@iab.org, ietf@ietf.org
Subject: Re: [rfc-i] Poll: RFCs with page numbers (pretty please) ?
Message-ID: <3F09EF2A87B102C8666C72D0@PSB>
In-Reply-To: <EB282B9A-8562-43B5-AC65-31FD2CF64C5D@ribose.com>
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.c om> <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org> <20201026150241.GK48111@faui48f.informatik.uni-erlangen.de> <20201026162814.GP39170@kduck.mit.edu> <20201026164036.GO48111@faui48f.informatik.uni-erlangen.de> <1a56dc3b-56ef-3ffb-a12b-44d5e0d0f835@levkowetz.com> <20201026171931.GP48111@faui48f.informatik.uni-erlangen.de> <b733240-fc78-5a71-8920-ff84fbf64287@iecc.com> <20201026180105.GQ48111@faui48f.informatik.uni-erlangen.de> <03976f9f-7f49-7bf7-ce29-ee989232a44d@gmail.com> <7FA8EF59-5CDE-42B9-A487-520531EEA1F0@juniper.net> <65374aef-e018-7bc8-ce50-d5c0a3982bf7@gmail.com> <DE3C9D6AE8EF94D87936DAE7@PSB> <75918E93-96A2-4C9A-9D60-570E7A0E1B22@ribose.com> <C393B7270B2043C75B6CA7B8@PSB> <EB282B9A-8562-43B5-AC65-31FD2CF64C5D@ribose.com>
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-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xAWmX0yS4VCMTsFGaCtxZgvF4f4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 27 Oct 2020 01:53:22 -0000


--On Tuesday, October 27, 2020 01:30 +0000 Ronald Tse
<tse@ribose.com> wrote:

> Thanks John for the clarification. There is some confusion to
> me whether the intention is just about the TXT output having
> page numbers, or for the PDF to also have the same page
> numbers, and whether to use page numbers inside cross
> references. There was a also discussion about a ToC and page
> numbers, but perhaps that was a diversion.
> 
> If the discussion is only about the ASCII output having page
> numbers, I have no objection because it is (nearly) purely
> cosmetic (in publication and in usage of the text, being done
> by xml2rfc).
> 
> If having page numbers will require the PDF output to also
> have page numbers, this inevitably leads to some shared spec
> between the TXT and PDF outputs on the topic of pagination,
> which is less ideal, but since I assume that is the work of
> xml2rfc, it's not a concern to us as tool maintainers.

Actually, I think you have it a bit backward.  The PDF has page
numbers today.  More to the point, PDF is (almost) inherently a
page image format so there is no way to escape pagination.  One
could decide to not number those pages in the footers, or one
could eliminate the headers and footers entirely, but the page
boundaries are going to be there regardless.

However, as long as a strict discipline is maintained that
references (within an RFC, between RFCs, and whatever we can
do/encourage about external references to RFCs use are to
section numbers and not pages (and there Brian and I agree)
_and_ as long as we don't allow sections to become so long that
people seek other mechanisms, then whether the page numbers in a
text format agree with those in the PDF format or not is largely
irrelevant.  That issue is centuries old: if I reference a
chapter by number in a book, that reference is typically stable
for different printings and formats (and often but not always
between editions).  But the page numbers often are not, so,
unless the people doing the layout are _really_ careful, using
the index from, e.g., a hardbound copy and trying to apply its
numbers to a paperback that uses different size type and page
layouts is, to use a technical term, just plain dumb.  And
external references that use page numbers need to be very
careful to specify exactly what form is being referred to.

> Adding page numbers to cross references can make reading
> confusing — since the cross references between the paginated
> and flowed versions will render these references differently.
> It's doable, but again this requirement ties the paginated
> versions (TXT and PDF) together for consistency.

And, again, this is why there has been a long-term prohibition
in the RFC Series against using page numbers in cross references.

> Of course, if the PDF output is simply an enhanced PDF-ized
> TXT version, these aren't really issues.

But two of several advantages of the contemporary (xml2rfc v3)
PDF version is that it can contain and render pictures easily
and that, if characters are used outside the ASCII repertoire,
they are rendered correctly as well.

best,
    john