[-- Attachment #1: Type: text/plain, Size: 217 bytes --] Hey list, 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? Cheers, - Marcelo. [-- Attachment #2: Type: text/html, Size: 291 bytes --]
[-- Attachment #1: Type: text/plain, Size: 473 bytes --] 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: application/pgp-signature, Size: 489 bytes --]
[-- 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 --]
Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:
> How was the process, from org file to tex to paper? I think it'd be
> nice if whoever did it (Carsten?) documented that on Worg. Org is
> amazing as a publishing platform (for books and ebooks), but I feel
> the information is still scattered around.
>
Unfortunately, the org documentation is not an org file: org.texi is the
primary file and it has always been a texinfo file. makeinfo is used to
turn it into an info file, and texi2pdf is used to turn it into a PDF
file (and thence to paper): see the org Makefile.
The reason is that org is part of emacs. The project *requires*
that documentation be provided in texinfo format.
Nick
Nick Dokos <nicholas.dokos@hp.com> writes:
> Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:
>
>> How was the process, from org file to tex to paper? I think it'd be
>> nice if whoever did it (Carsten?) documented that on Worg. Org is
>> amazing as a publishing platform (for books and ebooks), but I feel
>> the information is still scattered around.
>
> Unfortunately, the org documentation is not an org file: org.texi is the
> primary file and it has always been a texinfo file. makeinfo is used to
> turn it into an info file, and texi2pdf is used to turn it into a PDF
> file (and thence to paper): see the org Makefile.
Well, back in the olden days the documentation was simple plain text
inside of org.el which I eventually converted into a texinfo file.
Texinfo has some very nice features which at the time org-mode did not
even dream of having (it did not have an agenda and probably no
exporters).
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Hi Marcelo,
Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> How was the process, from org file to tex to paper?
Brian Gough might be the one to answer this.
Brian worked on improving org.texi by submitting a lot of
patches -- improving the syntax, etc. See Org's git history
around november-december 2010 to see these patches.
Then I guess Brian exported this to PDF (texi2pdf?) before
printing it.
But I don't know the details.
--
Bastien