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

Julian Reschke <julian.reschke@gmx.de> Mon, 26 October 2020 13:16 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 B1CA33A0121; Mon, 26 Oct 2020 06:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level:
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.247, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=gmx.net
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 lnAXxjrwmydu; Mon, 26 Oct 2020 06:16:20 -0700 (PDT)
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 0CC843A0ADF; Mon, 26 Oct 2020 06:16:20 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C04A5F40723; Mon, 26 Oct 2020 06:16:09 -0700 (PDT)
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 BC603F40723 for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 06:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 L55qxxOUV7jL for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 06:16:04 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by rfc-editor.org (Postfix) with ESMTPS id 5D163F40721 for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 06:16:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1603718172; bh=fIgX8Y9hhfHKMJDUbMgzRK0AxAwjCsyoNwwsauaN9GM=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Emx2+Jh9I2cQwdyo3kARQG8uSem6Cw7bImotVtgVvGbA5WmMjO96VXYO+xa+t1GEz RV0Saphy6cLGTxghkJlKcSOtjNXrLJE33gukTpHC0NSiEITZSEsxojf5QndSutgxcr EGiW1DBOc/LEhJp6f9tgSiU/GpqfYkBEczkw+eeY=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.236] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MQMuR-1kkSdR0y1Z-00MKki for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 14:16:12 +0100
To: rfc-interest@rfc-editor.org
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.com> <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <b1bd58b2-299b-d7bd-3d46-efd74151b7cd@gmx.de>
Date: Mon, 26 Oct 2020 14:16:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org>
X-Provags-ID: V03:K1:GvjfK1k87HjP4sU+DfitHwNJnBCti1C/78a1awENp00oW9VI+4f 5CovlwKkMnYPEF6BrXba/VV+TrIRfx5MT/KoWpxw210ehMVTH40udPSv6LoMHi2Iu7M2/O+ d44IwqlakMz6+A06iHwGv1MuFsZ4IyJomjbXl23WukLsna1uUm3ldp5hZvOrEw6dlviCizG TeVGiZLL6lVWjlqWmGQHQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:jAhMeoUUKXk=:bu4p6ShEyfoNWWtT69yGFy ayBhyUxtHvzMOIp94YaQtaj3v84xBixR7s5xGkJYJoJeyeQV2LuvPtQ+DOeNsXakoEoMI2moM oUPYTHGO0T9JJfRIUSkn2g63NKaaEmDblzQlQihZbrmsydwaYcXVVhfM2CqcqnlUx9veZLNyH ikt6IcjQ0nBssQVa+g7cklTNTWa3l8+OMMbTkTTKDXgz4CFygEXvQj2SqyAxBuIUBQieskkh4 ZZIdQUca8cClNxNVN8TWm3EZjOED+7C8OuCOl6Wsn3Dkmw5qTH8zExqDF47cS3HZuRKwC0jYf wiME/nVUiT21OAQBl0D4JqGt5IEJ7NZUSnKlpa1RH0chSf/0NeG+pyHyfLa2ckBy7PcC9TVaX KICoaNjSCiUjjxdaTijRSszFkNmpdF3KI0RYrlOVabtjnL+NvgIHMAdQb/2aa6pKw0UJ3j+rn PLqopBD5vbiS+ORGSQhIWHIuTgVx/ILQjDZpouTxGmJlPVTb09zYULg6DP6P/ri+YMp4iGOjE v+U0OLO/Wsfinpd1nq5c70S+ttC6JhL4RG5c/oMPSJm2iJuAYa7nKuLrnOOb2L2EZUZEivUHI EOt0qXTn4M3w7+Uhqm6lREfjrKbRt3eExceAv6MWcJMYHjbrQCZ15I38klXxBVWlbUMUWxTKI SCoMLYIPKiREdnNkDChy401tUVMvSvyQVLBacR1fYkx9fi+XZL9l/a9PY9zCUDbG36opUGJZt mhwsJVjgjdhY+UFHiRO9O2yyhQ8aZwvu0pDB/VmOuft4U1ckqZ8XXNNJit0E58lnH3K8qf7qP OZMpQUJp0TGiP5H4I+lPi/4+8HHI6NlhrwGptX7vOrRaiMBz2W4GmK5hsoguYCMsZbdkxHWfT u0KbM3w4IiBSuHJmsijg==
Subject: Re: [rfc-i] [irsg] Resending: Page numbers in RFCs questions / preferences
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>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Am 26.10.2020 um 13:55 schrieb Carsten Bormann:
> 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.)
> ...

Fun fact: RFC 7994 ("Requirements for Plain-Text RFCs") says in
<https://greenbytes.de/tech/webdav/rfc7994.html#rfc.section.4.2>:

"In order to retain similar content wherever possible between the
various publication formats, the table of contents will list section and
subsection numbers and titles but will not include page numbers."

But RFC 7995 ("PDF Format for RFCs") say in
<https://greenbytes.de/tech/webdav/rfc7995.html#n-similarity-to-other-outputs>:

"The table of contents (generated if the XML's <rfc> element's
tocInclude attribute has the value "true") [RFC7991] will have the
section number linked to the section start but will also include a page
number that is linked to the corresponding page. The section title and
the page number will be separated by a visually appropriate separator,
and the page numbers will be aligned with each other."

And, FWIW, RFC 7992 ("HTML Format for RFCs") says nothing about page
numbering. And that is the case not because it's not possible in HTML,
but just a CSS/output format issue. Given the right CSS (as produced by
rfc2629.xslt) and the right HTML-to-PDF converter (such as PrinceXML),
you will indeed get page numbers.

Best regards, Julian

PS: and yes, page numbers should not be used to refer to parts of the
RFC, because page breaks vary with output formats
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest