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

Paul Wouters <paul@nohats.ca> Thu, 06 May 2021 14:48 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 BDBB03A24E0 for <tools-discuss@ietfa.amsl.com>; Thu, 6 May 2021 07:48:57 -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 qFeaurVVEvev for <tools-discuss@ietfa.amsl.com>; Thu, 6 May 2021 07:48:53 -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 781963A24CC for <tools-discuss@ietf.org>; Thu, 6 May 2021 07:48:53 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4Fbc0L1x0nzCMG; Thu, 6 May 2021 16:48:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1620312530; bh=65KPb1Uf61mDeSAAG+WNGO1ILsjpIOh1Dv7P6s45c8k=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=kYfh1Rx0Fkv2+hNUbCBMB6+yASrqeIvCJ7Kxxyyiyg/9AJnVWjee+TIB+alfUdMAu s186Rb7fQtoBYnE9LRWLnYnRPJ19Tv06DIIG9F01G8NojV2XABXT7z+k9Jdu5qr0pG mK9c4E1SpiUnKU67QSo6Ek5u3z0ZVHjLYHGrcINU=
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 yPLu1miUSmhI; Thu, 6 May 2021 16:48:49 +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; Thu, 6 May 2021 16:48:48 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id C265C510E3; Thu, 6 May 2021 10:48:47 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C123B510E2; Thu, 6 May 2021 10:48:47 -0400 (EDT)
Date: Thu, 06 May 2021 10:48:47 -0400
From: Paul Wouters <paul@nohats.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: tools-discuss@ietf.org
In-Reply-To: <8DF71730-F34D-41D1-863F-2CDCACEBEB21@tzi.org>
Message-ID: <f59b84b-8165-c09b-6827-f75b1d2f56d@nohats.ca>
References: <3b649680-b123-781b-e81b-f129f2a146fe@nohats.ca> <8DF71730-F34D-41D1-863F-2CDCACEBEB21@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/3OwWobdzp30Nc7eHWnPs86NVVJw>
Subject: Re: [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 14:48:59 -0000

On Thu, 6 May 2021, Carsten Bormann wrote:

>> <artwork>    struct {
>>        uint16 ExtSupportLifetime;
>>        opaque AuthenticationChain&lt;1..2^16-1&gt;;
>>    } DnssecChainExtension;
>> </artwork>
>
> That is what <[CDATA[ sections are good for:
>
> <artwork><![CDATA[
>  struct {
>      uint16 ExtSupportLifetime;
>      opaque AuthenticationChain<1..2^16-1>
>  } DnssecChainExtension;
> ]]></artwork>

Ahhh, I have used (copied it from others) before. I didn't realise I
needed it here! But the markdown didn't generate that ofr me.

> Care linking to the specific file?

https://tools.ietf.org/html/draft-dukhovni-tls-dnssec-chain-05

That is me tweaking the xml and txt artisanally though. The original .md
file (and the Makefile with my sanitizing hacks) is at:

https://github.com/vdukhovni/dnssec-chain-extension

> I don’t know which rfc markdown stuff you are referring to (there is a choice!), but see above for what is generated by rfc-kramdown.

Yes rfc-kramdown :)

> We wouldn’t have got to RFC 9000 if what you are experiencing were a common problem, so we do need to know some details.

I'm sure it's me, and you've already helped me a step in the right
direction. Thanks!

Paul