forked from jgm/lunamark
-
Notifications
You must be signed in to change notification settings - Fork 36
Support programmatic text in YAML metadata values #440
Copy link
Copy link
Closed
Labels
conversion outputRelated to the output format of the Markdown-to-TeX conversionRelated to the output format of the Markdown-to-TeX conversionluaRelated to the Lua interface and implementationRelated to the Lua interface and implementationplaintexRelated to the plain TeX interface and implementationRelated to the plain TeX interface and implementationyamlRelated to the tinyyaml library.Related to the tinyyaml library.
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
conversion outputRelated to the output format of the Markdown-to-TeX conversionRelated to the output format of the Markdown-to-TeX conversionluaRelated to the Lua interface and implementationRelated to the Lua interface and implementationplaintexRelated to the plain TeX interface and implementationRelated to the plain TeX interface and implementationyamlRelated to the tinyyaml library.Related to the tinyyaml library.
Currently, we assume that all strings in YAML metadata are markdown text. Besides the
jekyllDataStringrenderers, we should also produce e.g.jekyllDataProgrammaticStringrenderers, which would receive the raw text of the strings. Furthermore, we should also renamejekyllDataStringrenderers to e.g.jekyllDataTypographicStringand deprecate the previous name.Tasks
jekyllDataProgrammaticStringrenderer and renderer prototype.jekyllDataProgrammaticStringrenderer and renderer prototype.jekyllDataStringrenderers and renderer prototypes tojekyllDataTypographicString.jekyllDataStringsimilarly to Rename renderers based on the semantics of elements #201.CHANGES.md.CHANGES.mdandREADME.md.