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

Carsten Bormann <cabo@tzi.org> Thu, 06 May 2021 14:56 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 ECD803A2511 for <tools-discuss@ietfa.amsl.com>; Thu, 6 May 2021 07:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 0TWhbrj23Gm0 for <tools-discuss@ietfa.amsl.com>; Thu, 6 May 2021 07:56:15 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C08F3A2510 for <tools-discuss@ietf.org>; Thu, 6 May 2021 07:56:15 -0700 (PDT)
Received: from client-0175.vpn.uni-bremen.de (client-0175.vpn.uni-bremen.de [134.102.107.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Fbc8s2N7Mz14PM; Thu, 6 May 2021 16:56:13 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f59b84b-8165-c09b-6827-f75b1d2f56d@nohats.ca>
Date: Thu, 06 May 2021 16:56:12 +0200
Cc: tools-discuss@ietf.org
X-Mao-Original-Outgoing-Id: 642005772.8881429-3b021af317f48692026e3b78500e7c41
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5466F89-9793-4309-B835-903CE7984D3C@tzi.org>
References: <3b649680-b123-781b-e81b-f129f2a146fe@nohats.ca> <8DF71730-F34D-41D1-863F-2CDCACEBEB21@tzi.org> <f59b84b-8165-c09b-6827-f75b1d2f56d@nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/sm17emEq7L_nSDvYtjfIt_4oMUc>
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:56:20 -0000

On 2021-05-06, at 16:48, Paul Wouters <paul@nohats.ca> wrote:
> 
> 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.

To clarify, you are talking about the tool called mmark.

>> 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 :)

I was trying to say kramdown-rfc, but misstated.
(Kramdown-rfc and mmark are the two markdown-to-rfc tools available right now.)

>> 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. 

Great!

Grüße, Carsten