Re: [Tools-discuss] mangled ToC in RFC 8784

Michael Richardson <mcr@sandelman.ca> Wed, 28 October 2020 20:00 UTC

Return-Path: <mcr@sandelman.ca>
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 BCD1B3A08AD for <tools-discuss@ietfa.amsl.com>; Wed, 28 Oct 2020 13:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eoP6moEXBLNY for <tools-discuss@ietfa.amsl.com>; Wed, 28 Oct 2020 12:59:59 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA9053A0846 for <tools-discuss@ietf.org>; Wed, 28 Oct 2020 12:59:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id BF4C7389E3; Wed, 28 Oct 2020 16:06:40 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zjg-_yobsv62; Wed, 28 Oct 2020 16:06:38 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 65367389E1; Wed, 28 Oct 2020 16:06:38 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4D29E4F5; Wed, 28 Oct 2020 15:59:55 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: tools-discuss@ietf.org
cc: Henrik Levkowetz <henrik@levkowetz.com>, Paul Wouters <paul@nohats.ca>
In-Reply-To: <438c0bc7-ceed-c77b-4846-75f26e477ae9@levkowetz.com>
References: <alpine.LRH.2.23.451.2010281420240.2537787@bofh.nohats.ca> <438c0bc7-ceed-c77b-4846-75f26e477ae9@levkowetz.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 28 Oct 2020 15:59:55 -0400
Message-ID: <6756.1603915195@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Eg9dAC-oS3EGLYkBNrd24YMyoR0>
Subject: Re: [Tools-discuss] mangled ToC in RFC 8784
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: Wed, 28 Oct 2020 20:00:01 -0000

Henrik Levkowetz <henrik@levkowetz.com> wrote:
    > On 2020-10-28 19:21, Paul Wouters wrote:
    >>
    >> Hi,
    >>
    >> https://tools.ietf.org/html/rfc8784
    >>
    >> This RFC seems to have a mangled ToC that cannot be clicked at.
    >>
    >> Is that something that can be fixed?

    > Probably yes.  The biggest stumbling block is that with the current
    > un-paginated RFC text format, there is nothing or not much to distinguish
    > ToC lines from start-of-section lines later in the document, which is
    > an issue for the regex-based (~ stateless) htmlization script.

    > The line of spaced dots between section name and page number in earlier
    > ToCs were used to identify ToC entries.

    > I think I can figure out a way to deal with this, but it will require some
    > coding, testing, and a new release of my htmlization lib.

I gotta ask if it's worth fixing?

Maybe we need a new output option for xml2rfc that produces this text-like
output that we seem to prefer.  Or maybe it's just a CSS variation?

(For along time, I've prefered the tools htmlized pages: they were the best
for pulling offline onto a tablet for reading.  The apps that I used for
doing that have rotted, and COVID has made that less interesting)

The RFC editor copy of HTML looks great, and it links to that, and the ToC
works there.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [