toerless
commented
2 years ago Hi David
I have actually never tried to insert graphics into draft/RFCs, mostly because in the recent ones i didn't have any such good graphical material. And i think its a widely underused/underdocumented option. And maybe its even over-regulated, aka: in the end some process will tell us we can not do it as we may like to do it.
Here is an example you may want to clone:
https://datatracker.ietf.org/doc/html/rfc7893
It has in its PDF nice colorful graphics, and in their place in the txt and any other rendering only placeholder blocks. And it has some text pointing readers to use the PDF rendering to see the graphics. This is the type of example RFC from which i would clone the formatting for such PDF-only pictures (maybe there are newer RFCs using the same tricks).
You can see the XML formatting used in the RFCs draft XML file:
https://www.ietf.org/archive/id/draft-ietf-pals-congcons-02.xml
Now, i do not know which tool to use to get the PDF rendering, and i also do not know if/how it would be possible to have a markdown file that does create the desired XML, but:
How about you first try to hack in the XML required by hand and see if you can generate a PDF with the image inlined - because i am pretty sure that you would need to upload both the xml and the pre-rendered PDF to datatracker if you wanted the PDF correctly rendered on data tracker
Once you know that step, we can ask a markdown expert whether or how the necessary XML can be created from markdown.
If any of these tooling steps turns out to be too cumbersome for the draft versions, I would suggest you just create the placeholder ascii-art in markdown and fill it with:
a) a URL to a github location of the png image b) [RFC-editor please insert png image into PDF rendering of RFC] instructions for RFC editor.
Aka: Don't bother with a complex tool-chain during writing of the draft versions, but push it down the road to the time when the RFC is being built, and just have the right text and URL pointer in the document to make sure this happens once the doc goes RFC.
Only downside is that readers of the draft will have to click on the URL and then can only see the picture in a separate browser window (big deal ;-).
Cheers Toerless
On Mon, Mar 28, 2022 at 03:00:21AM -0700, David von Oheimb wrote:
As suggested by @toerless on Friday, I tried adding an image extracted from the presentation, but cannot recall how I was supposed to do this.
When I add it as an image to the MarkDown source file like this:
then
kdrfc --v3 draft-ietf-anima-brski-async-enroll.mdfails like this:
draft-ietf-anima-brski-async-enroll.xml(595): Error: Did not expect element xref there, at /rfc/middle/section[4]/section[2]/xref draft-ietf-anima-brski-async-enroll.xml(595): Error: Element section has extra content: xref, at /rfc/middle/section[4]/section[2]/xref /home/david/Siemens/proj/PKI/anima-brski-async-enroll-internal/draft-ietf-anima-brski-async-enroll.xml(15): Error: Invalid document before running preptool. Unable to complete processing draft-ietf-anima-brski-async-enroll.xmlDoes it make sense in such a way after all, or how else to add the image?
-- Reply to this email directly or view it on GitHub: https://github.com/anima-wg/anima-brski-async-enroll/issues/22 You are receiving this because you were mentioned.
Message ID: @.***>
--
@.***
mcr
HBrock
DDvO
As suggested by @toerless on Friday, I tried adding an image extracted from the presentation, but cannot recall how I was supposed to do this.
When I add it as an image to the MarkDown source file like this:
then
fails like this:
Does it make sense in such a way after all, or how else to add the image?