From: tsd@tsdye.com (Thomas S. Dye)
To: SW <sabrewolfy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Outline structure and LaTeX
Date: Sun, 20 May 2012 07:43:18 -1000 [thread overview]
Message-ID: <m1zk92n3yh.fsf@tsdye.com> (raw)
In-Reply-To: <loom.20120520T120314-761@post.gmane.org> (SW's message of "Sun, 20 May 2012 10:13:51 +0000 (UTC)")
Aloha SW,
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.
>
>
>
Org mode can export to various formats. Export to LaTeX works well, but
it helps to know LaTeX when something unwanted happens. One of the
other export options might better suit your needs.
There are some examples of academic documents prepared with Org mode
that might help you follow the LaTeX export path,
e.g. http://www.jstatsoft.org/v46/i03,
http://orgmode.org/worg/org-contrib/babel/uses.html#sec-6.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2012-05-20 17:43 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 [this message]
2012-05-29 8:04 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1zk92n3yh.fsf@tsdye.com \
--to=tsd@tsdye.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.