From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: SW <sabrewolfy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Outline structure and LaTeX
Date: Tue, 29 May 2012 17:34:48 +0930 [thread overview]
Message-ID: <87txyzpg4f.fsf@ucl.ac.uk> (raw)
In-Reply-To: <loom.20120520T120314-761@post.gmane.org> (SW's message of "Sun, 20 May 2012 10:13:51 +0000")
SW <sabrewolfy@gmail.com> writes:
> I'm preparing an academic document with several chapters. The text will
> eventually exist as a LaTeX document. However, I am doing my early planning and
> writing directly in an org file, making use of the structure elements (*, **,
> ***, etc) to provide structure and entering text for the relevant sections in
> the appropriate place.
>
> Org is a huge project and I have not explored every aspect and every contributed
> extension. Is there a "best practice" approach for what I am doing? Should I
> write directly in LaTeX rather? Is there an easy conversion process from an
> outlined document to LaTeX? I know there org can export to LaTeX. Would that be
> the best option? It has not worked well for me previously -- page breaks
> appeared in the wrong place and other pages has text that flowed over the end of
> the page.
I used to write all my papers etc. in LaTeX. I now use org almost
exclusively, using LaTeX directly only for letters. With the advances
in the LaTeX export engines (both the "stable" one and the new one
Nicolas is working on), I am able to work completely in org and only
worry about exporting to LaTeX at the end, when ready to submit.
For instance, this paper:
http://www.sciencedirect.com/science/article/pii/S0306261911006507
was written completely in org and the resulting LaTeX file exported by
org was sent *as is* to the publisher (Elsevier, in this case).
The best thing, for me, about using org to write papers is that I can
have all my data, notes, musings, etc. in the same document and only
export the content that I want to export. Add babel to the mix and my
analysis is also within the same document. And include inline tasks and
I can even have task management in the document. Brilliant!
In terms of /best practice/, my advice in using org would be the same as
I would give if you were to write in LaTeX directly: don't tilt at
windmills! Instead of trying to micro-manage the document, concentrate
on the content. Unless you have very specific typesetting requirements,
e.g. from the publisher, let org+LaTeX do its thing. Usually, what
comes out looks much better than what you could do manually.
If things need fixing, do it at the end when the *content* is
finalised. Org allows you to concentrate on the content without too
much clutter, actually very little clutter.
Addressing your question more specifically, I don't understand your
comment about page breaks. LaTeX is usually very good about page
breaks, especially with respect to line widows etc.
Finally, there are quite a few people on this list that use org to
create LaTeX documents and they're all quite friendly so ask away if you
have any specific questions.
HTH,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 + Ma Gnus v0.6
next prev parent reply other threads:[~2012-05-29 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 10:13 Outline structure and LaTeX SW
2012-05-20 17:43 ` Thomas S. Dye
2012-05-29 8:04 ` Eric S Fraga [this message]
2012-05-29 9:10 ` Giacomo M
2012-05-29 9:17 ` SW
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=87txyzpg4f.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=sabrewolfy@gmail.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).