News for hackers. Stuff that matters.

A comment on Reach for Markdown, not LaTeX. Parent comment

Re:Reach for Markdown, not LaTeX by eslaught on Saturday February 17, 2018 @11:54PM (#16404521)
Have you ever tried to typeset a complex document with side bars, figures, multi-part figures, figures that contain math (not just images), and layouts that take a lot of tweaking to get just right?

I can imagine doing that in Pandoc Markdown, but only with extensive use of raw LaTeX code. Most of the above doesn't have a direct equivalent even in richer Markdown dialects like Pandoc.

[ Parent | on HN ]
Re:Reach for Markdown, not LaTeX by mwcampbell on Sunday February 18, 2018 @12:06AM (#16404550)
Ah, thanks for educating me. I pity anyone who has to work within the constraints of print in 2018. To me, hypertext that adapts to the user's device and needs (e.g. rendering at a different font size and reflowing appropriately, or rendering through non-visual means like speech and braille) is the only way to go these days.
[ Parent | on HN ]
Re:Reach for Markdown, not LaTeX by Gracana on Sunday February 18, 2018 @12:12AM (#16404568)
To be fair to latex, the majority of hypertext examples don't do any of those things either.
[ Parent | on HN ]
Re:Reach for Markdown, not LaTeX by swfsql on Sunday February 18, 2018 @08:21AM (#16405943)
It's harder to make fine adjustments, such as those made by the microtype latex package.
[ Parent | on HN ]