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

[Carsten Bormann <[e-mail]>]

Hi Paul,

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

(This example generated by “the rfc markdown stuff”.)

> but the rendered html (from www.ietf.org/staging/) displays:
> 
>    struct {
>        uint16 ExtSupportLifetime;
>        opaque AuthenticationChain&lt;1..2^16-1&gt;
>    } DnssecChainExtension;

Care linking to the specific file?

The specific example above generates this html for me:

<div class="artwork art-text alignLeft" id="section-1-10">
<pre>
  struct {
      uint16 ExtSupportLifetime;
      opaque AuthenticationChain&lt;1..2^16-1&gt;
  } DnssecChainExtension;
</pre><a href="#section-1-10" class="pilcrow">¶</a>
</div>

Which renders as attached below (not sure that will make it through this ML).

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

As it should.

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

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.

Grüße, Carsten