IETF Logo Mail Archive

Re: [Tools-discuss] pages numbers in ToC in PDF

Toerless Eckert <tte@cs.fau.de> Thu, 27 May 2021 23:48 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E043A18E5 for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 16:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 zHYy27kZeiOe for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 16:48:01 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 2A6893A18E4 for <tools-discuss@ietf.org>; Thu, 27 May 2021 16:48:01 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id A8C14548004; Fri, 28 May 2021 01:47:53 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id A1FF34E75C3; Fri, 28 May 2021 01:47:53 +0200 (CEST)
Date: Fri, 28 May 2021 01:47:53 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: John Levine <johnl@taugh.com>, tools-discuss@ietf.org
Message-ID: <20210527234753.GF3909@faui48e.informatik.uni-erlangen.de>
References: <20210527200341.4D2858D61D0@ary.qy> <93518243-3705-42AE-9B57-6F1BDF30853C@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <93518243-3705-42AE-9B57-6F1BDF30853C@gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/_JjpznbqOfsz3RgYvYvF4Aiu31Q>
Subject: Re: [Tools-discuss] pages numbers in ToC in PDF
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 23:48:06 -0000

On Thu, May 27, 2021 at 04:33:43PM -0700, Bob Hinden wrote:
> As others have noted, it seems to me that if the rendering has page numbers, then the TOC should too.
> 
> However, looking at RFC 8995, at https://www.rfc-editor.org/info/rfc8995, there are rendering for HTML, TEXT and PDF.   HTML and TEXT have no page numbers, PDF does.   Personally I find the Text version without page number (on pages and TOC) ugly and not very useful.
> 
> I would prefer we add page number back in all of the renderings.  Sigh...

For HTML, TEXT its not only page numbers, its also to add back pagination.
PDF is the odd man of, because it has pagination but yet no page numbers (in TOC).

As i said, unless someone from the tools teams offers something better, its
got to be an RFC to be written to ask for it. However, that will fail if
it does not make it clear that paginated TXT/HTML will only be ADDITIONAL
renderings to be requested for on on datatracker or rfc-editor (whatever tools team
prefers). Otherwise we would have an unwinnable battle.

Cheers
    toerless
> 
> Bob
> 
> 
> 
> > 
> > xml2rfc uses a library called wasyprint to create the PDFs. It renders
> > HTML, using a tweaked version of the HTML output. That limits our
> > control over the output and is why the page breaks often look strange.
> > We knew about the limitations when we chose that approach, albeit
> > perhaps not just how bad the page breaks would be, because it is
> > vastly easier than the alternative of writing a PDF rendering engine.
> > 
> > R's,
> > John
> 



> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss


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

v2.23.0 | Report a Bug | By Email