Images in Mmark are somewhat complicated, not in the least, because XML2RFC needs to output both HTML and text. To make that work you can specify multiple images in an artset and the renderer will pick the correct one, depending on the output.
To include artwork/source/images, you can:
Use a code block. If this has a language specified, it will become a sourcecode otherwise a will be an artwork.
With Mmark you can, generate Internet-Drafts when writing for the IETF (mmark), generate manual pages (mmark -man), create HTML pages (mmark -html) and generate markdown again (mmark -markdown); great for formatting documents.
See here how to start writing documents.
Mmark version 2.0.0 has been released!
This means it is considered feature complete and stable.
Any syntax that creates fishy HTML5 or the wrong RFC 7791/RFC 7749 output is considered a bug and should be fixed.
Mmark is a powerful markdown processor written in Go, geared towards writing IETF documents. It is, however, also suited for writing complete books and other technical documentation, like the Learning Go book (mmark source, and I-D text output).
Also see this repository on how to write RFC using Markdown.
It provides an advanced markdown dialect that processes file(s) to produce internet-drafts in XML RFC 7991 format. Mmark can produce xml2rfc (aforementioned RFC 7991), RFC 7749 (xml2rfc version 2 - now deprecated), HTML5 output, markdown and manual pages.
Mmark Frequently Asked Questions.
How Do I Create an Independent IETF Document? Use the following as starting point for your title block, ipr and submissiontype are the important settings here.
title = "Title" abbrev = "Title" ipr = "none" submissiontype = "independent" keyword = [""] [seriesInfo] name = "Internet-Draft" value = "draft-00" stream = "independent" status = "informational" How Do I Create an IRTF Document? Set submissiontype and stream in seriesInfo to IRTF.
This is version 2 of Mmark: based on a new markdown implementation and some (small) language changes as well. We think these language changes lead to a more consistent user experience and lead to less confusion.
See changes from v1 if you’re coming from version 1.
Including files is now done relative to the file being parsed (i.e. the sane way). Block attributes apply to block elements only.