Hacker News
Pandoc Templates
ifh-hn
|next
[-]
At the time I'd not got round to understanding the yaml front matter etc. I even user Zettlr for a while [0].
I then discovered quarto [1] and this changed everything. Much nicer experience. I used this for my masters papers.
I think the tooling around pandoc is what makes it such a good tool. I remember attempting restructured text and latex and having a right hard time.
Loic
|root
|parent
|next
[-]
Quarto is my documentation tool.
For me, they are both massively used, but cover different usages.
thibaut_barrere
|root
|parent
|previous
[-]
apwheele
|root
|parent
[-]
I don't even know what magic buttons I need to push to get that template to correctly inherit the table format I wanted from pandoc, but it does. I tend to have other scripts though for more complicated tables though. So if I want a table to have a certain row highlighted a different color, I would write a Powershell script to run after the table was generated.
I was never able to figure out how to use LibreOffice to insert the table of contents and then export to PDF (although I can do it via the GUI).
ktzar
|next
|previous
[-]
I keep thinking that modern text editors are just flawed and markdown, with all its downsides and limitations, is what 99% is the people need.
noosphr
|root
|parent
|next
|previous
[-]
If you want a pure markup language that is simple, plain text readable and able to produce text more complex than what a type writer could manage in 1920 then restructured text is the way to go.
abyssin
|root
|parent
|next
|previous
[-]
maxerickson
|root
|parent
|previous
[-]
I mean, they don't want to think about building the output, never mind controlling the process.
limagnolia
|root
|parent
|next
[-]
maxerickson
|root
|parent
[-]
Unfortunately, most people don't use paragraph styles, but if you do, it's a couple clicks.
sgc
|root
|parent
[-]
kzrdude
|root
|parent
|next
|previous
[-]
troyvit
|root
|parent
|previous
[-]
My markdown resume has its own problems but having this level of control has been a huge load off my mind.
chlaunchla
|next
|previous
[-]
Table layouts were often broken, with text overlapping into adjacent fields. Unicode font fallback didn't work properly, with characters like "→" being silently dropped because they didn't exist in the main font. Having predictable control of page breaks, to avoid situations where header text didn't stick to the following paragraph and instead had header and paragraph text split over a page boundary, was pretty much impossible.
I ended up concluding that Markdown isn't a sufficiently powerful markup language for page-based documents, and went back to using Word in all its WYSIWYG delight.
That said, maybe there were ways of doing all of the above but I couldn't figure it out and found the whole process of wrestling with with both Markdown and LaTeX templates, and Pandoc configuration, unintuitive and annoying.
__mharrison__
|root
|parent
|next
[-]
In fact, just had a friend with a traditionally published book who is now self-pubbing ask me yesterday about my tools. I recommended Pandoc and Typst. He (surprisingly to me) had never heard of Typst, but within the hour replied that (with the use of AI) he had a great-looking template for the book. (Try doing that with LaTeX).
cwmoore
|root
|parent
|next
|previous
[-]
https://stackoverflow.com/questions/1664049/can-i-force-a-pa...
thibaut_barrere
|next
|previous
[-]
falsaberN1
|next
|previous
[-]
Oh no, inspiration has arrived. Guess I know what I'm wasting my weekend into, hah.
Also this page seems to have existed for a while and I never heard of it! I'm glad I stumbled upon this. A lot of nice ideas here.
malteg
|next
|previous
[-]
thibaut_barrere
|root
|parent
|next
[-]
wodenokoto
|next
|previous
[-]
ckarpati
|next
|previous
[-]
FailMore
|next
|previous
[-]
submeta
|next
|previous
[-]
I would be lost had I have to use the Office tools to edit and format my text.
So thank you to all the maintainers of Pandoc.
ltrg
|root
|parent
|next
[-]
Embarrassingly, a horrible little script for converting Pandoc's Markdown endnotes to inline format remains my most-starred GitHub repo: https://github.com/ltrgoddard/inliner/
maxerickson
|root
|parent
|next
|previous
[-]
If you are using markdown, you already understand the conceptual basis for it, so you just need to understand how it's implemented over there.
I'm not arguing that it is something you should do, just rolling my eyes at "I would be lost".