emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: XeCycle <xecycle@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: The org paper manual - tools used
Date: Wed, 5 Oct 2011 15:50:55 -0500	[thread overview]
Message-ID: <CACHMzOEmwaWVW=HzEXo400G12wZqgpvZdYmsqiosXYpOoCz+DA@mail.gmail.com> (raw)
In-Reply-To: <878vp0m474.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

How was the process, from org file to tex to paper? I think it'd be nice if
whoever did it (Carnsten?) documented that on Worg. Org is amazing as a
publishing platform (for books and ebooks), but I feel the information is
still scattered around.

- Marcelo.

On Tue, Oct 4, 2011 at 11:51 PM, XeCycle <xecycle@gmail.com> wrote:

> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> > Hey list,
> Hello.
> > The paper org manual was an exciting idea. I might buy one soon.
> > I was wondering how was the editing work involved in turning it
> > into paper-published book? What tools did you guys use?
> TeXinfo, I think.
> --
> Carl Lei (XeCycle)
> Department of Physics, Shanghai Jiao Tong University
> OpenPGP public key: 7795E591
> Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591

[-- Attachment #2: Type: text/html, Size: 1239 bytes --]

  reply	other threads:[~2011-10-05 20:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 20:44 The org paper manual - tools used Marcelo de Moraes Serpa
2011-10-05  4:51 ` XeCycle
2011-10-05 20:50   ` Marcelo de Moraes Serpa [this message]
2011-10-05 21:46     ` Nick Dokos
2011-10-06  6:32       ` Christian Egli
2011-10-29 10:46     ` Bastien

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='CACHMzOEmwaWVW=HzEXo400G12wZqgpvZdYmsqiosXYpOoCz+DA@mail.gmail.com' \
    --to=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=xecycle@gmail.com \


* 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


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