(Markdown) YAML metadata block (Pandoc extension)
Omikhleia opened this issue · 3 comments
I could possibly see interesting uses for Pandoc's yaml_metadata_block extension, would it be supported. We'd first have too define/restrict which bits of such a metadata block to use. It also perhaps needs to distinguish between documents processed from the command-line (where one could want to define, e.g., paper size, main fonts, PDF metadata etc.) from documents \include'd in other documents (where such choices would likely have to be ignored, but where other settings could be however still needed, e.g. additional fonts and fallbacks)
The "problems" with metadata blocks are numerous:
- There's no formal standard definition (for fonts, metadata, paper size, etc.), rather some loose ad hoc usage: e.g. what Pandoc + LaTeX accept... with lots of idiosyncrasies), what some blog or static site generators use, etc?
- Each document may have its own block, with unclear semantics where several documents are included in a book.
- It's a Markdown extension, but has not support (at this date) in Djot.
Besides, I am working on a "master document" format in the Resilient collection (Omikhleia/resilient.sile#18) which should cover most of the needs expressed above.
= This "enhancement" here is possibly rejected, or would need more a better rationale (for different use cases)
On the Djot side, there are also discussions regarding metadata -- and this is at best messy for now.
We do no need that mess.
As stated above, going for rejection -- There's no plan to work on it at this level.