From: Peter Davis <pfd@pfdstudio.com>
To: John Hendy <jw.hendy@gmail.com>, Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Resume: Squeezing lines tighter in LaTeX output?
Date: Sat, 18 Apr 2015 13:45:54 -0400 [thread overview]
Message-ID: <55329852.2080104@pfdstudio.com> (raw)
In-Reply-To: <CA+M2ft__0ao0UrMNTeFjVssW4S559i+JjNA7oNYVi4n1gv_1Pg@mail.gmail.com>
On 4/18/15 1:27 PM, John Hendy wrote:
> On Fri, Apr 17, 2015 at 7:18 PM, Marcin Borkowski <mbork@mbork.pl> wrote:
>> On 2015-04-17, at 20:13, John Hendy <jw.hendy@gmail.com> 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
next prev parent reply other threads:[~2015-04-18 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 17:28 Resume: Squeezing lines tighter in LaTeX output? Peter Davis
2015-04-17 18:13 ` John Hendy
2015-04-17 19:13 ` Peter Davis
2015-04-17 20:10 ` John Hendy
2015-04-18 0:18 ` Marcin Borkowski
2015-04-18 2:20 ` Peter Davis
2015-04-18 7:02 ` Marcin Borkowski
2015-04-20 8:23 ` Eric S Fraga
2015-04-18 17:27 ` John Hendy
2015-04-18 17:45 ` Peter Davis [this message]
2015-04-18 18:08 ` Marcin Borkowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55329852.2080104@pfdstudio.com \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
--cc=mbork@mbork.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).