From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: mike.mclean@pobox.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Org as a publishing toolkit
Date: Wed, 11 May 2011 11:10:50 -0500 [thread overview]
Message-ID: <BANLkTi=enLxdDCme8aHe55qimsHkun7VDA@mail.gmail.com> (raw)
In-Reply-To: <4DCAA7FE.6000802@pobox.com>
Thanks for the tip Mike. I had no idea about this approach, I'm still
too naive in TeX/LaTeX. I'll definitely have to get my head around
both -- but it's reassuring to know that I can write the content in
orgmode and tweak the LaTeX output it later as I want.
By the way, any book recommendations ? I'd like something that could
lay down the foundations and not take too much time. Also, not sure if
I should start with TeX or LaTeX.
Thanks!
Marcelo.
On Wed, May 11, 2011 at 10:15 AM, Mike McLean <mike.mclean@pobox.com> wrote:
> On 5/10/11 1:52 PM, Marcelo de Moraes Serpa wrote:
>> Hi list,
>>
>> So today I have been reseaching about higher-levels toolkits that
>> could help me get into TeX (and or LaTeX) and at the same time
>> allowing me to keep the text in a more human-readable format (easier
>> to mantain and to convert to other formats if needed).
>>
>> I know that if I want beautiful formatted PDFs I will need to get into
>> TeX / LaTeX, and I already started doing that, but as I said, keeping
>> the text in a higher level format has benefits that you already know
>> about.
>>
>> So I looked at asciidoc, the lower-level XML-based docbook, markdown,
>> pandoc, ConTeXt, etc.
>>
>> Then I thought, why not try orgmode?
>
> I've done the same thing over the past few months and agree that
> org-mode as the front end for a LaTeX document production system is the
> way to go. The low-level tweak that I've added is a definition of a set
> of LaTeX custom classes that map to my "roles" in life. For example, I
> am the president of a non-profit organization and I have a LaTeX class
> for that organization. This class defines chapter heads, title pages,
> etc. to have a look-and-feel of the organization. I have a day job, the
> LaTeX class for that reflects the corporate communication guidelines.
> (And so on).
>
> I had tried the route of defining various low-level LaTeX tweaks in
> header statement in org export option files, and this was wayyyyy to
> complex, fragile, and very difficult to maintain. The time I spent the
> last few weeks creating 3 (of 4) necessary LaTeX =.cls= files has so far
> been time well spent. I would strongly recommend thinking about putting
> any desired low-level LaTeX tweaks into a class (or set of classes) that
> are *your's*.
>
>
>
next prev parent reply other threads:[~2011-05-11 16:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 17:52 Org as a publishing toolkit Marcelo de Moraes Serpa
2011-05-10 18:31 ` Thomas S. Dye
2011-05-10 18:48 ` Marcelo de Moraes Serpa
2011-05-10 19:19 ` Thomas S. Dye
2011-05-10 20:53 ` Marcelo de Moraes Serpa
2011-05-10 21:35 ` Thomas S. Dye
2011-05-10 21:39 ` Marcelo de Moraes Serpa
2011-05-10 22:26 ` Thomas S. Dye
2011-05-11 0:41 ` Marcelo de Moraes Serpa
2011-05-11 1:40 ` prad
2011-05-11 4:52 ` Avdi Grimm
2011-05-11 8:09 ` Rasmus
2011-05-12 6:52 ` Eric S Fraga
2011-05-11 15:15 ` Mike McLean
2011-05-11 16:10 ` Marcelo de Moraes Serpa [this message]
2011-05-11 16:33 ` Nick Dokos
2011-05-14 12:32 ` Mike McLean
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='BANLkTi=enLxdDCme8aHe55qimsHkun7VDA@mail.gmail.com' \
--to=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mike.mclean@pobox.com \
/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).