John/rsoc: Re: Page numbers in RFCs questions / preferences

Toerless Eckert <tte@cs.fau.de> Mon, 26 October 2020 17:19 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 93AD23A0D98 for <wgchairs@ietfa.amsl.com>; Mon, 26 Oct 2020 10:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 oDlo8hjdTijR for <wgchairs@ietfa.amsl.com>; Mon, 26 Oct 2020 10:19:37 -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 3C6C03A0DD8 for <wgchairs@ietf.org>; Mon, 26 Oct 2020 10:19:36 -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 12C0D54860E; Mon, 26 Oct 2020 18:19:32 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0CD4E440059; Mon, 26 Oct 2020 18:19:32 +0100 (CET)
Date: Mon, 26 Oct 2020 18:19:32 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: ietf@johnlevine.com, rsoc@iab.org
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Benjamin Kaduk <kaduk@mit.edu>, WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
Subject: John/rsoc: Re: Page numbers in RFCs questions / preferences
Message-ID: <20201026171931.GP48111@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> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1a56dc3b-56ef-3ffb-a12b-44d5e0d0f835@levkowetz.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/eqwU0gJnrhLda-Dm6zj30OW2XgA>
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 17:19:39 -0000

Hi John/RSOC,

Could you please explain why RSOC does not want to permit the ability
to have paginated RFC output options ? Also, where and when was this
discussed with the community ?

Thank you!
    Toerless

P.S.: Thanks, Henrik

On Mon, Oct 26, 2020 at 06:11:12PM +0100, Henrik Levkowetz wrote:
> Hi,
> 
> xml2rfc currently supports pagination of .txt output for drafts, but not
> for RFCs.  This is a limitation originally requested by the RFC editor, in
> the specification for the v3 text formatter work for RFCs.
> 
> A couple of months ago, prompted by multiple requests for the ability to
> produce paginated .txt output for RFCs, I asked for permission to enable
> pagination also for RFCs, but in the end the RSOC answered that they did
> not want to make it possible to generate paginated .txt output for RFCs.
> 
> John Levine should be able to give further information.
> 
> I'd be perfectly happy to add the ability; given that it's available for
> drafts it's trivial from a technical viewpoint.
> 
> 
> Best regards,
> 
> 	Henrik
> 
> On 2020-10-26 17:40, Toerless Eckert wrote:
> > Thanks, Ben. 
> > 
> > Then i guess it shouldn't be too hard for the tools team to
> > offer at least on tools.ietf.org beside the existing formats one
> > with e.g.: text with pagination...
> > 
> > I guess i'll have to ask Henrik how best to proceed.
> > 
> > Cheers
> >     Toerless
> > 
> > On Mon, Oct 26, 2020 at 09:28:14AM -0700, Benjamin Kaduk wrote:
> >> On Mon, Oct 26, 2020 at 04:02:41PM +0100, Toerless Eckert wrote:
> >> > 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 ?
> >> 
> >> IIRC the xml2rfc tool already supports the pagination functionality with a
> >> command-line argument, so you can make your own right now.
> >> Unfortunately, I was unable to find the exact incatation in the mail
> >> archives within the time I allotted for searching.
> >> 
> >> -Ben
> > 
> 




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