emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Resume: Squeezing lines tighter in LaTeX output?


From: Peter Davis
Subject: Re: [O] Resume: Squeezing lines tighter in LaTeX output?
Date: Sat, 18 Apr 2015 13:45:54 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0


On 4/18/15 1:27 PM, John Hendy wrote:
On Fri, Apr 17, 2015 at 7:18 PM, Marcin Borkowski <address@hidden> wrote:
On 2015-04-17, at 20:13, John Hendy <address@hidden> wrote:

Everything you'll do in Org will simply involve passing the right
parameters to LaTeX via Org. In other words, you should start by
Personally, I prefer configuring on the LaTeX side, but this is because
I find it much easier.
Could you clarify "on the LaTeX side" (as in, post-Org, or LaTeX
altogether)? Or what you find easier? I think I'm probably on the same
page, but just wanted to hear your take. For me it comes down more to
the command/"micro-formatting" side. As in, for my resume, I went raw
LaTeX as it would have been ridiculous to try and do what I wanted
from Org (aka, I'd have just had #+begin/end_latex everywhere and thus
Org would literally just be a middle man). But if I'm using Org at
all, I prefer to figure out how to do the LaTeX stuff from Org;
otherwise when I inevitably miss something (typo, syntax, format
tweak) I have to re-export, then re-apply all my custom LaTeX tweaks
to the resultant .tex file.
This is absolutely my view. I want to keep the "source" in org format, and just be able to generate HTML, LaTeX/PDF or text automatically and without manual tweaking. I'm actually somewhat more familiar with LaTeX than with org-mode, which is why I asked in the first place.

I've been able to get a nice clean PDF from a hand-editing LaTeX file, but that's not what I needed here. Another problem is that many of the sites that allow you to upload a resume expect a simple hierarchical structure, and don't seem to do a good job with tables and other layout controls.

Another difficulty with using some of the LaTeX packages with org is that they define new commands and environments, but then you have to invoke these commands and/or environments each time you want to use them, and I don't know a way (if there is one) of getting org to do that without getting into the situation John describes of using org as a thin wrapper around LaTeX.

Thanks for all the replies and suggestions. I'm pretty close now, but just need to fine tune the parameters a bit, which is pretty typical when dealing with LaTeX.

-pd


For most reports and such, I don't adjust things that finely, and so
~5-10 #+latex_header lines seems completely worth it to have access to
markup vs. writing all that raw LaTeX. Plus it just looks nicer :)

finding out how to do what you want to do in LaTeX; for example google
"how to change line spacing latex" and peruse the top result:
- http://en.wikibooks.org/wiki/LaTeX/Paragraph_Formatting
Be cautious, though: the LaTeX wikibook has some parts which are very
outdated (at least this was the situation when I looked at it some time
ago).  I'd rather recommend searching CTAN and searching/asking at
TeX.StackExchange.

Good to know! I wasn't aware of that and tend to just go for the first
google hit, which can sometimes be wikibook, but absolutely is often a
tex.SE Q/A.

Definitely look at paralist and enumitem for tweaking spacing as a
starting point.
Also, check out the titlesec package (http://www.ctan.org/pkg/titlesec)
and/or memoir and/or koma-script.

Hope that helps.
John
Best,
Thanks for the input!
John

--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University


--
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]