emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Thomas Herbert <mashdot@toshine.net>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Professional PDF LaTeX templates?
Date: Wed, 16 Mar 2011 09:37:03 +0000	[thread overview]
Message-ID: <871v27be4g.fsf@ucl.ac.uk> (raw)
In-Reply-To: <AANLkTi=PyCBG5zktW-ys6Ym6XoQ07nYnOHg3zZh6MwGw@mail.gmail.com> (John Hendy's message of "Tue, 15 Mar 2011 21:52:15 -0500")


>> 2011/3/14 Thomas Herbert <mashdot@toshine.net>
>>>
>
>>> Afternoon,
>>>
>>> I wonder if anyone had any good examples of org-mode LaTeX templates with
>>> which to export professional looking PDFs?
>>>
>>> It is my big issue with org-mode at the moment, and I have tried reading
>>> what I can on LaTeX styling but it is getting to the point that I am
>>> spending way to much time trying to learn enough LaTeX only to find I can't
>>> translate it into anything that looks the quality of using MS Word and Adobe
>>> Flashpaper.

Not intending to start a flame war but my experience is that latex, even
with everything at default settings, beats a typical MS Word document
hands down!  At least in academic circles, many publishers use latex for
the final typesetting stage even if the original article was submitted
in MS Word.

The negative aspect, for some, about latex is that everything is
customisable (as you have alluded to) given that it is but a set of
macros built on top of the TeX typesetting system (thank you Donald
Knuth!).  Because the underlying system is both robust and
comprehensive, anything is possible!  The power of TeX comes partly from
the basis being both page and paragraph formatting, as opposed to line
by line formatting which tools like MS Word use.

Therefore, I am curious as to what you wish to achieve:

John Hendy <jw.hendy@gmail.com> writes:
> Instead... could you provide something you think is professional to
> set the bar and those on the list can either match it or point you in
> the direction of something they've seen or already created to fit into
> your genre of "professional"?

This would indeed be very useful.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.55.g87c42.dirty)

  reply	other threads:[~2011-03-16  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 16:27 Professional PDF LaTeX templates? Thomas Herbert
2011-03-16  2:24 ` Camille persson
2011-03-16  2:52   ` John Hendy
2011-03-16  9:37     ` Eric S Fraga [this message]
2011-03-16 10:41       ` Scot Becker
2011-03-17 20:34 ` Rasmus
2011-03-17 20:52   ` Thomas S. Dye
  -- strict thread matches above, loose matches on Subject: below --
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
2011-03-17 12:06   ` Russell Adams

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=871v27be4g.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=mashdot@toshine.net \
    /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).