jgm/pandoc

Markdown to LaTeX: Level 6 Heading

Open

#8,069 opened on May 13, 2022

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Haskell (44,133 stars) (3,850 forks)batch import
enhancementformat:LaTeXgood first issuetemplateswriter

Description

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.

Contributor guide

Tech stack
None
Domain
documentation
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of pandoc's writer architectureFamiliarity with LaTeX document class
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the LaTeX writer module in pandoc, specifically the function that handles heading levels. Look at how level 5 is implemented (using \subparagraph) and replicate for level 6 using a custom \subsubparagraph macro. Also examine the default.latex template to add the macro definition. The issue comments may contain further discussion. Consider that the author does not know Haskell, so the solution may require assistance from maintainers.