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

Toerless Eckert <tte@cs.fau.de> Thu, 27 May 2021 20:23 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 6ACC13A0E01 for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 13:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, 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 3wsi2qZOdNew for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 13:23:27 -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 F2C0A3A0E00 for <tools-discuss@ietf.org>; Thu, 27 May 2021 13:23:26 -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 D7089548017; Thu, 27 May 2021 22:23:15 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id CB4B84E75C0; Thu, 27 May 2021 22:23:15 +0200 (CEST)
Date: Thu, 27 May 2021 22:23:15 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, tools-discuss@ietf.org
Message-ID: <20210527202315.GY3909@faui48e.informatik.uni-erlangen.de>
References: <27379.1622115270@localhost> <20210527185057.GW3909@faui48e.informatik.uni-erlangen.de> <71809401-C8A7-43D6-829C-2D665FEA9F7D@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <71809401-C8A7-43D6-829C-2D665FEA9F7D@tzi.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/tv-B0AO2D7oLkjOXNJhfSnSl5Fw>
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 20:23:31 -0000

Thanks, i was thinking this wuould be possible to do in .txt given
how its done for drafts.

Obviously what i meant was in the context of ietf tools/data-tracker offering such a
rendering. Having everyone doing it by themselves.

On Thu, May 27, 2021 at 09:18:29PM +0200, Carsten Bormann wrote:
> On 2021-05-27, at 20:50, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > Thats my understanding. If there is an easier way to get page numbers into TOCs
> > of PDF, that would be great.
> 
> A first step might be a patch for xml2rfc.
> Note that xml2rfc can already put pagination in TXT, which is an option that needs to be explicitly specified.
> https://xml2rfc.tools.ietf.org/xml2rfc-doc.html#section-b.7-1.11
> This apparently was possible to do without changing RFCXXXX.
> 
> https://trac.ietf.org/trac/xml2rfc/ticket/558
> seems to imply this cannot be done for PDF in the current architecture of xml2rfc.
> Having used troff extensively for a quarter of a decade, I can authoritatively confirm that it sure can be done, at the cost of double (*) the processing time.
> (One implementation of the concept is called a ???side file???, and, no, that cannot be googled, but every TeX user knows it.)
> 
> Grüße, Carsten
> 
> (*) and, occasionally, triple that, but I don???t think that applies here.