emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: 'Mash <mashdot@toshine.net>
Cc: nicholas.dokos@hp.com,
	Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Professional PDF LaTeX templates?
Date: Wed, 16 Mar 2011 10:54:18 -0400	[thread overview]
Message-ID: <14953.1300287258@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from 'Mash <mashdot@toshine.net> of "Wed, 16 Mar 2011 11:04:29 -0000." <20110316110429.19583tdvlcfb6y4g@webmail.tuffmail.net>

'Mash <mashdot@toshine.net> wrote:

> I suppose by "professional" I really meant "polished", and so it is
> LaTeX styling I have having trouble with, it may also be laziness on
> my part. I have tried searching for LaTeX styling which I can
> translate into a few org-mode header declarations but still can't work
> out what is or is not compatible with org-mode (LaTeX classes) or how
> to implement styling correctly.
> I think what it is that I have been using CSS for so long that I am
> getting frustrated in not being able to produce the level of results I
> want in LaTeX. Also I feel like a complete numpty not being able to
> clearly understand how to build and define external LaTeX classes I
> can call to output my simple .org file to a "polished" .pdf. I.e.
> margins, line-heights, different block element font styling, common
> graphical page headers or footers.
> There are a huge amount of LaTeX examples on the web, but they are
> full documents with inline elements, I wanted to know if anyone has
> already setup classes that work, with notes on LaTeX dependencies (and
> how and where to download them from) which they use day to day to
> produce reports, articles, contracts or client proposals from simple
> .org files?
> Is that any clearer?

Not really.

Both Eric Fraga and John Hendy have given valid answers to how one goes
about it: you settle down to *one* kind of document that you want to
produce (take the simplest one and leave the rest for later), then
either learn enough LaTeX to be able to produce it or cajole/beg/hire
somebody to do it for you, and *then* figure out how to use org to produce
the LaTeX needed to produce that kind of document.

The trouble is that neither org nor LaTeX are black boxes whose insides
you can afford to ignore. With the approach outlined above, at the end
of the process, you *will* have a (blackbox-like) almost automatic way of
going from org to "professional" output, but it is fragile in the sense
that if you want to change something, you will need to implement the
change in LaTeX first, and once you are satisfied with the output, you
will need to go back and tweak the org mechanisms to produce that.
Then you can shut your eyes again and pretend that it's a black box.

So learn some LaTeX: once you get past the initial hump (the mechanics
of producing output), then it's not only fairly easy, it also starts
making sense. Having a desired output (keep it simple!) is going to make
that an enjoyable journey too. And once you touch down on LaTeX island,
and become comfortable, you'll either never leave or you'll want to
visit again and again!

And as John pointed out, people here are fairly easy to cajole into helping
you :-)


  parent reply	other threads:[~2011-03-16 14:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 11:04 'Mash
2011-03-16 13:54 ` John Hendy
2011-03-16 14:10 ` Eric S Fraga
2011-03-16 14:43   ` 'Mash
2011-03-16 14:57     ` Eric S Fraga
2011-03-16 14:54 ` Nick Dokos [this message]
2011-03-17 12:06   ` Russell Adams
  -- strict thread matches above, loose matches on Subject: below --
2011-03-14 16:27 Thomas Herbert
2011-03-16  2:24 ` Camille persson
2011-03-16  2:52   ` John Hendy
2011-03-16  9:37     ` Eric S Fraga
2011-03-16 10:41       ` Scot Becker
2011-03-17 20:34 ` Rasmus
2011-03-17 20:52   ` Thomas S. Dye

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:

  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=14953.1300287258@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mashdot@toshine.net \
    --subject='Re: Professional PDF LaTeX templates?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).