[Tools-discuss] placing < and > in artwork renders broken html

Paul Wouters <paul@nohats.ca> Thu, 06 May 2021 02:31 UTC

Return-Path: <paul@nohats.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 78BC03A2BF9 for <tools-discuss@ietfa.amsl.com>; Wed, 5 May 2021 19:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 47AtUWrcFhM2 for <tools-discuss@ietfa.amsl.com>; Wed, 5 May 2021 19:31:17 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49ED83A2BF7 for <tools-discuss@ietf.org>; Wed, 5 May 2021 19:31:17 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4FbHdF3rnrzKHk for <tools-discuss@ietf.org>; Thu, 6 May 2021 04:31:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1620268273; bh=RboH+B0zT9YUxsOc2VJDo+rNxKPmJdCmUB3j5UaRMmg=; h=Date:From:To:Subject; b=T6j7CTWcWnoajB+P2bj2O/lLZTliX1+V12Y8ar7VAUnk8cAqz3yUIlNIuRHNE206i 8vq1Gj69r4wNjTe3pGIe8YZQx1vjvWiJpHSVLR8Jbylxo1GmU1/9u9WjOXde+p09uI +zyMZ0w3pFv3o1TdtxtdiOHBRCUjLKdaHjC8Xb6A=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id rmNh23YHQ9Is for <tools-discuss@ietf.org>; Thu, 6 May 2021 04:31:12 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <tools-discuss@ietf.org>; Thu, 6 May 2021 04:31:12 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id CB6294FD32; Wed, 5 May 2021 22:31:10 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C43424FD31 for <tools-discuss@ietf.org>; Wed, 5 May 2021 22:31:10 -0400 (EDT)
Date: Wed, 05 May 2021 22:31:10 -0400
From: Paul Wouters <paul@nohats.ca>
To: tools-discuss@ietf.org
Message-ID: <3b649680-b123-781b-e81b-f129f2a146fe@nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/avRo3pMr_NoWwqvZqn_Tln2VKpo>
Subject: [Tools-discuss] placing < and > in artwork renders broken html
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, 06 May 2021 02:31:23 -0000

I have an issue with artwork that renders badly in html on the site:


<artwork>    struct {
         uint16 ExtSupportLifetime;
         opaque AuthenticationChain&lt;1..2^16-1&gt;;
     } DnssecChainExtension;
</artwork>


I am expecting to see:

        struct {
            uint16 ExtSupportLifetime;
            opaque AuthenticationChain<1..2^16-1>
        } DnssecChainExtension;


but the rendered html (from www.ietf.org/staging/) displays:

     struct {
         uint16 ExtSupportLifetime;
         opaque AuthenticationChain&lt;1..2^16-1&gt;
     } DnssecChainExtension;


If use literal < or >, then xml2rfc complains and won't render my .txt output.

Worse but unrelated, the rfc markdown stuff generates &amp;lt; _and_
changes all quotes to &quot; and yes these two bugs amplify each other.

I hope someone in the future can fix all the badly rendered html format in RFCs/drafts.

Paul