Re: [Tools-discuss] Robert: opening bug against rfcmarkup (was: Re: Hyperlinks to sections/subsections in current RFC HTML format)

Carsten Bormann <cabo@tzi.org> Wed, 16 June 2021 05:13 UTC

Return-Path: <cabo@tzi.org>
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 086D03A4B8E for <tools-discuss@ietfa.amsl.com>; Tue, 15 Jun 2021 22:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 nrO0cz5IIvMN for <tools-discuss@ietfa.amsl.com>; Tue, 15 Jun 2021 22:13:41 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [134.102.50.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94B6A3A4B8F for <tools-discuss@ietf.org>; Tue, 15 Jun 2021 22:13:41 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4G4YHj21bwz2xHy; Wed, 16 Jun 2021 07:13:37 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20210616010247.GX12022@faui48e.informatik.uni-erlangen.de>
Date: Wed, 16 Jun 2021 07:13:36 +0200
Cc: Robert Sparks <rjsparks@nostrum.com>, Julian Reschke <julian.reschke@gmx.de>, tools-discuss@ietf.org
X-Mao-Original-Outgoing-Id: 645513216.852537-08b619a456ff6d9d86de579eb33335e0
Content-Transfer-Encoding: quoted-printable
Message-Id: <E40E1371-E8F8-4B9D-B67B-8C041CFF627E@tzi.org>
References: <20210616010247.GX12022@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/QvVR8SR-AEvgRLvf4Kap0XLscpU>
Subject: Re: [Tools-discuss] Robert: opening bug against rfcmarkup (was: Re: Hyperlinks to sections/subsections in current RFC HTML format)
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, 16 Jun 2021 05:13:47 -0000

The bug is that we are still using rfcmarkup to generate the htmlized versions.
That was needed in the age of nroff, but since RFC 8650 it is really weird to throw away all the information that the XML has during rendering and then try to guess it back into existence in rfcmarkup.

xml2rfc should have an “htmlized” writer, which generates the same layout in the output as the text writer, just in the way that rfcmarkup has been doing it, but with information from the horse’s mouth.

Grüße, Carsten