Writing Scientific Documents Using LaTeX (2009) [pdf]
mirror.unicorncloud.org
mirror.unicorncloud.org
ShareLaTeX also provide a very useful LaTeX learn wiki [4], and my co-founder at Overleaf created this three part introductory course [5].
Hope this helps anyone getting started, and feedback on Overleaf/ShareLaTeX is always appreciated if you've used it previously.
[2] https://www.sharelatex.com
[3] https://www.overleaf.com/blog/518-exciting-news-sharelatex-i...
[4] https://www.sharelatex.com/learn
[5] https://www.overleaf.com/latex/learn/free-online-introductio...
1. It's fragile. Documents I wrote in 2010 no long "build" with the latest TeXLive release, and fixing and debugging my documents has been a huge time sink. With something like a flora or plant list, that needs to be updated periodically with new information, getting sidetracked by breakage can be very frustrating.
2. I've found it's a lot quicker and simpler for me to write in MS Word and then (if needed) import into Adobe InDesign to style my writing. This combination also seems to work better with the citation software I prefer (Papers).
Do you have any general guidelines as to why?
Did you use obscure packages or features that no longer exist?
I had been thinking one of the greatest things about the book I am almost finished is that it will serve as a template for me for decades.... maybe I was wrong.
In order to reply to this message with some facts, I just rebuilt my phd thesis for the first time in 17 years using a modern TeXLive with nary a LaTeX issue. The only effort needed was to re-learn my own work flow and to install some old tool I used to post-process the PostScript.
I'd hazard that LaTeX has better shelf life, in terms of rebuilding, than say C.
It was due to a conflict between packages (memoir and morefloats) the only seems to happen in recent version of LuaLaTeX. My Lua code was not directly involved, as far as I can tell.
A lot of students will shy away from coding prefering more hands on work in the lab. Some students will use Matlab or LabVIEW to perform some essential task and hate every minute of it. It might be some stastical analysis they don't understand built with spaghetti code they've inherited, or it might be for controlling a contrary piece of lab equipment. Either way they feel threatened by it or don't want to spend the time learning to understand it.
Show them a basic LaTeX document and how it can make writing papers and, importantly their thesis, much easier than the horror show that is Word and suddenly there is a moment of wonder.
Oh god, when I was an undergrad we had to spend a semester of junior/senior year doing an applied stint in a physics lab on campus, and I still have nightmares about the decade old Frankenstein's monster of a LabVIEW document that was thrown in my lap... trying to debug thousands of nodes in this flat data flow nightmare while interfacing with shaky equipment held together with scotch tape was horrific.
I immediately noped out to applied math.
I've begun using it to write a lot of my notes, since TeXMacs has sadly been failing lately, and to be honest it's wonderful having human-readable text along with a document that compiles nicely to a PDF with all the bells and whistles.
All the nice looking output if latex but all the nice features of emacs and orgmode.
1) Tables are hard. There must be a more visual way do layout a table.
2) All your documents look like a scientific paper. It doesn't have beautiful styles which you can include and have a completely different layout. Like you can do with Word templates.
Does LaTex improved in the last ten years? Or we all must be content with markdown?
For point 2, this is still the case.
LaTeX is really what you make of it. It can look like anything you want. It's just a matter of which styles/packages you use, which options you select, how much tweaking you do, and how much knowledge/help you have when trying to make it look the way you want it to.
Regarding 2), you can nowadays find a wealth of document styles to use, if you don't want your writing to look like a CS paper... While creating proper document classes is a non-trivial amount of work (and so it is in MS Word and other WYSIWYG tools), it can then greatly simplify the task of creating the documents themselves. For example, I have recently done a CV class ( https://github.com/mvarela/orbit-cv ), which provides a bunch of macros to automate the creation of your CV/résumé, and looks nothing like a scientific paper...
Regarding 2), there are many document classes that don't look like scientific papers although LaTeX ships a limited number of document classes (book, article, report, and letter). Here are two third-party classes that come to my mind:
- https://ctan.org/pkg/hitec is a nice class that is
- https://www.ctan.org/pkg/tufte-latex is inspired by Edward Tufte's books and provides a similar-looking handout/book style.
And here is a list of some other classes: http://texcatalogue.ctan.org/bytopic.html#classes
Things like gutters and margins are precisely controlled, can be different for left and right pages, etc.
The ability to define your own macros, that can be used through the doc.
The ability to use conditionals within your document, so it's easy to produce say a print-ready pdf and an epub from the same source.
Really, really easy to put your doc unto source control (cvs or git) and get legible diffs.
IMHO, if you are printing a major document or book for professional purposes, you want to use latex.