Live data from Hacker News

Introducing non-technical people to LaTeX

texblog.net

11–20 of 26 posts

Re: Introducing non-technical people to LaTeX

#11
I never "learned" LaTeX, despite being an academic mathematician and using it all the time. My documents have headers which I don't understand. Indeed, learning it from scratch seems like a hassle, and it has features far beyond what I ever use.

I simply obtained a document that was similar to what I was trying to create, made a copy, and then changed the content.

Re: Introducing non-technical people to LaTeX

#12
post #6

My suggestion: teach people how to use Markdown and then use markdown2pdf (which first converts to Latex and then to PDF).

That doesn't work too well when writing for a conference or journal with a predefined template and style file. The obvious solution -- do all your writing in Markdown and then integrate at the very end of the workflow -- doesn't work too well because you can't tell how long the document is until you use the real template.

Same goes for org-mode's Latex export.

Re: Introducing non-technical people to LaTeX

#13
post #3

My response to this post is, what on earth for? While you can use LaTeX for a ridiculous number of things [1][2][3], LaTeX is primarily a tool for typesetting technical documents. Note that word "technical" in there; why would a non-technical person want that? It's complex; you have to type ridiculous things like "\textbf" to get bold text, and "\begin{enumerate}" to make a simple list. It's complicated; you have to…

I agree that the error messages are dreadful, but I've found a pretty simple pedagogical approach to make them less terrifying for a new learner. The key is that you reinforce a habit of frequently hitting the "typeset" button that way, when something goes wrong, they know to look at the commands that they just typed.

If you combine that habit with an explanation of the more common errors (like forgetting an "end" tag, or using improper nesting), then the error messages become a lot less scary. The learner, at least initially, doesn't have to try to understand what the message means, just how to deal with it.

Re: Introducing non-technical people to LaTeX

#14
Don't forget Lyx! In fact, I will take this opportunity to give a huge thank you to the developers and communities of Lyx, BibTex, BibDesk, Tex, Latex, Open Office, and NeoOffice. With their tools and online documentation, my wife just self-published a book, including a correctly formatted Kindle edition. She is generally not technical, but was able to figure out a workflow that worked for her and produced a really good looking product. I think she dealt directly with "code" exactly once (separating "front matter" from "main matter" in Lyx). Thanks!

Re: Introducing non-technical people to LaTeX

#15
post #5

I've taught around 20 non-technical people LaTeX. I would say that these are all good tips. But really, the only thing a non-technical person needs to learn LaTeX is to have someone sit down with them and teach them 1 on 1. I have a fairly refined lesson at this point, and can successfully teach anyone LaTeX in 45 minutes to an hour and a half, depending on how quickly they get it. I've taught mostly undergraduates (…

> Biology

What would be the problem? I've both written papers in Latex and Word, but cannot think of a discipline-related advantage.

Re: Introducing non-technical people to LaTeX

#16
post #14

Don't forget Lyx! In fact, I will take this opportunity to give a huge thank you to the developers and communities of Lyx, BibTex, BibDesk, Tex, Latex, Open Office, and NeoOffice. With their tools and online documentation, my wife just self-published a book, including a correctly formatted Kindle edition. She is generally not technical, but was able to figure out a workflow that worked for her and produced a really g…

(sorry for the self-reply) For the curious: Lyx working document + (BibDesk+BibText+LaTex+Tex) -> really nice PDF for printing. Lyx -> ODF -> NeoOffice -> Amazon Kindle toolset -> Kindle book. For backup/recovery, she relied on the built-in revision control in Lion (based on Time Machine, I think).

Re: Introducing non-technical people to LaTeX

#17
post #5

I've taught around 20 non-technical people LaTeX. I would say that these are all good tips. But really, the only thing a non-technical person needs to learn LaTeX is to have someone sit down with them and teach them 1 on 1. I have a fairly refined lesson at this point, and can successfully teach anyone LaTeX in 45 minutes to an hour and a half, depending on how quickly they get it. I've taught mostly undergraduates (…

> Biology What would be the problem? I've both written papers in Latex and Word, but cannot think of a discipline-related advantage.

The big one, as I understand it, is inserting nice looking tables for ANOVA results. Both Stata and SAS can output their results tables to LaTeX.

Re: Introducing non-technical people to LaTeX

#18
post #12
post #6

My suggestion: teach people how to use Markdown and then use markdown2pdf (which first converts to Latex and then to PDF).

That doesn't work too well when writing for a conference or journal with a predefined template and style file. The obvious solution -- do all your writing in Markdown and then integrate at the very end of the workflow -- doesn't work too well because you can't tell how long the document is until you use the real template. Same goes for org-mode's Latex export.

Actually, it is acceptably straightforward to include a custom header in org-mode. Basically you can create your own latex class in customize-group org-export-latex and then add a

#+LATEX-HEADER: \input{stuff.tex}

to your file to include the appropriate header magick. I'm currently using this approach to prepare my thesis in org-mode.

Re: Introducing non-technical people to LaTeX

#19
i sense a disconnect in the premise. do non-technical people really need latex? - to invest the time to study prettyness of presentation... depends on definition, scope and degree of technical'ness but generally i'd think they (should) focus on quality of content in their own field because it's just much cheaper to outsource the nonessentials (latex being one of them) to more competent experts who dedicate lifetimes to 'making the presentation pretty'

Re: Introducing non-technical people to LaTeX

#20
I've long felt that LaTeX is unnecessarily complex for most users. The output is undeniably attractive but there's considerable pain involved in getting there.

It's because LaTeX is old and its ubiquity has caused the field to stagnant for decades. It's an area ripe for disruption, but it's tricky due to the amount of complexity involved.

Post reply on HN