You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I understand Markdown defines headings upto 6 levels, to correspond to h1-h6 in HTML.
When Pandoc is converting a level 5 heading it is converted to \subparagraph{}, while a level 6 heading is just converted to plain text.
I think it would be better to have a level 6 heading wrapped in a \subsubparagraph{} macro, while having something like \newcommand\subsubparagraph[1]{#1} in default.latex. That way it would preserve the previous behavior, while also making it possible to write templates that modify the behavior of level 6 headings. This would help people like me who are writing templates for converting markdown to pdf.
I don't know haskell yet, so I can't really submit a pull request.
The text was updated successfully, but these errors were encountered:
Sure. I'm not completely sure about this one, since \subsubparagraph isn't standard LaTeX, but it gets requested often enough. I think it might be a good idea to put the relevant code under a conditional in the template, and only include it if the document actually has level-6 headings (we do something similar with math, see stMath in WriterState).
As far as I understand Markdown defines headings upto 6 levels, to correspond to
h1
-h6
in HTML.When Pandoc is converting a level 5 heading it is converted to
\subparagraph{}
, while a level 6 heading is just converted to plain text.I think it would be better to have a level 6 heading wrapped in a
\subsubparagraph{}
macro, while having something like\newcommand\subsubparagraph[1]{#1}
in default.latex. That way it would preserve the previous behavior, while also making it possible to write templates that modify the behavior of level 6 headings. This would help people like me who are writing templates for converting markdown to pdf.I don't know haskell yet, so I can't really submit a pull request.
The text was updated successfully, but these errors were encountered: