Re: [rfc-i] Problem with Kramdown tooling and figures?

["Paul Duffy (paduffy)" <paduffy=[e-mail]>]

FYI a quick kramdown test using a correct example from the templates...

<figure>
  <name>Test Figure</name>
  <artset>
    <artwork type="svg" src="https://www.rfc-editor.org/materials/format/svg/stream.svg" />
  </artset>
</figure>

... results in the following XML ...

        <figure/>
        <name>Test Figure</name>
        <artset>
          <artwork type="svg" src="https://www.rfc-editor.org/materials/format/svg/stream.svg"/>
        </artset>
        <t>&lt;/figure&gt;</t>

Manually repairing that XML ... I am able to generate a PDF containing the IETF sample SVG.

Attempt to generate a text document from the XML results in a bunch of errors (see attached).


-----Original Message-----
From: rfc-interest <[e-mail]> On Behalf Of Paul Duffy (paduffy)
Sent: Wednesday, June 8, 2022 10:24 AM
To: Jay Daley <[e-mail]>
Cc: [e-mail]; RFC Interest <[e-mail]>
Subject: Re: [rfc-i] Problem with Kramdown tooling and figures?

Understood thank you.  

Do note the older templates appear early in a Google search.  I've bookmarked the new.

Friendly reminder that all of this is precursor to producing a kramdown draft containing several complex SVG figures (another smelly kettle of fish).  My diagraming tool vendor is working to support the IETF SVG variant.

Cheers


-----Original Message-----
From: Jay Daley <[e-mail]> 
Sent: Wednesday, June 8, 2022 9:24 AM
To: Paul Duffy (paduffy) <[e-mail]>
Cc: [e-mail]; RFC Interest <[e-mail]>
Subject: Re: [rfc-i] Problem with Kramdown tooling and figures?

Thanks Paul

From Carsten’s response it looks as if this is an issue with upstream kramdown so the following is for info only.

Those templates are unfortunately very out of date and have been replaced with new templates here https://authors.ietf.org/en/templates-and-schemas.  Apologies for the confusion, but it has taken longer to redirect tools.ietf.org than expected and we have no mechanism to update it in the interim.  The redirection should be complete by IETF 114.

cheers
Jay


> On 8 Jun 2022, at 14:01, Paul Duffy (paduffy) <[e-mail]> wrote:
> 
> Sure.
> 
> Starting at line 114 here ... view-source:https://tools.ietf.org/tools/templates/draft-davies-template-bare-07.xml
> 
> -----Original Message-----
> From: Jay Daley <[e-mail]> 
> Sent: Wednesday, June 8, 2022 6:48 AM
> To: Paul Duffy (paduffy) <[e-mail]>
> Cc: [e-mail]; RFC Interest <[e-mail]>
> Subject: Re: [rfc-i] Problem with Kramdown tooling and figures?
> 
> Hi Paul
> 
>> On 8 Jun 2022, at 05:23, Paul Duffy (paduffy) <paduffy=[e-mail]> wrote:
>> 
>> Hi Carsten
>> 
>> Per our previous conversation, I will be incorporating SVG graphics into my kramdown draft.
>> 
>> But I first tested the tooling with a very simple figure example lifted from one of the XML draft templates.  
> 
> Can I ask which of the templates you used?
> 
> cheers
> Jay
> 
>> 
>> Cheers
>> 
>> -----Original Message-----
>> From: rfc-interest <[e-mail]> On Behalf Of Carsten Bormann
>> Sent: Tuesday, June 7, 2022 6:51 PM
>> To: Paul Duffy (paduffy) <paduffy=[e-mail]>
>> Cc: RFC Interest <[e-mail]>
>> Subject: Re: [rfc-i] Problem with Kramdown tooling and figures?
>> 
>> Hi Paul,
>> 
>>> On 7. Jun 2022, at 22:32, Paul Duffy (paduffy) <paduffy=[e-mail]> wrote:
>>> 
>>> I have a Kramdown draft with the following figure attempt ...
>>> 
>>> <figure anchor="xml_happy">
>>> <artwork align="left" name="" type="" alt=""><![CDATA[
>>> +-----------------------+
>>> | Use XML, be Happy :-) |
>>> |_______________________|
>>>    ]]></artwork>
>>> </figure>
>>> 
>>> XML result from  https://author-tools.ietf.org/ …
>>> 
>>> <figure anchor="xml_happy"/>
>>> <artwork align="left" name="" type="" alt="">&lt;![CDATA[
>>> +-----------------------+
>>> | Use XML, be Happy :-) |
>>> |_______________________|
>>> ]]&gt;</artwork>
>> 
>> When I try this I get a couple of error messages:
>> 
>> - Found no end tag for 'figure' (line 575) - auto-closing it
>> - Found invalidly used HTML closing tag for 'figure' on line 581
>> 
>> …and a different (similarly broken) XML output, too; I’d probably need the whole document to reproduce this.
>> 
>> Clearly, something isn’t working the way we want it to with the XML (HTML) parsing in kramdown here (kramdown is the markdown engine on which kramdown-rfc was built).
>> 
>> Of course, the fix is to just write:
>> 
>> ~~~
>> +------------------------------+
>> | Use markdown, be Happier :-) |
>> |______________________________|
>> ~~~
>> {: #xml_happy}
>> 
>> But you probably had a reason why you wanted to put in your XML manually…
>> 
>> The mailing list to discuss this further is [e-mail] (or maybe a GitHub issue on https://rfc.space).
>> 
>> Grüße, Carsten
>> 
>> _______________________________________________
>> rfc-interest mailing list
>> [e-mail]
>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
>> _______________________________________________
>> rfc-interest mailing list
>> [e-mail]
>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
> 
> -- 
> Jay Daley
> IETF Executive Director
> [e-mail]
> 

-- 
Jay Daley
IETF Executive Director
[e-mail]

_______________________________________________
rfc-interest mailing list
[e-mail]
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest

_______________________________________________
rfc-interest mailing list
[e-mail]
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest