From: "Dr. Arne Babenhauserheide" <firstname.lastname@example.org>
To: "Juan Manuel Macías" <email@example.com>
Subject: Re: Org as a book publisher
Date: Sun, 07 Mar 2021 18:46:44 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3188 bytes --]
I’ve been going that route for a few years now, and I setup an autotools
pipeline with all the little tweaks and hacks I needed to make
everything work well together.
I’m using LaTeX (pdflatex), scribus, calibre and imagemagick to publish
a roleplaying book with charactersheet,
Maybe some of it can help you. The entrypoints are the Makefile, the
setup, and the configure.ac (for the hacks):
The main document is
I also have some derived documents that use the included tables as data.
Most complex example:
> I would like to share here two samples of one of the most intense uses
> that I give Org Mode: for typesetting, layout and editorial design. In
> other words, I use Org (and Org-Publish) where publishers today use DTP
> proprietary software like InDesign or QuarkXpress (a type of software,
> on the other hand, that was never intended to compose books but rather
> magazines, posters, brochures and so on). The samples are from a book
> on classical philology, recently published here in Spain, and from a
> fairly extensive dictionary, still work in progress:
> Naturally, what acts in the background here is TeX and LaTeX
> (specifically Lua(La)TeX), so what I really do is use Org and
> Org-Publish as a sort of high-level interface for LaTeX. But I don't
> mean to avoid LaTeX: in fact, I've been working with LaTeX for a long
> time. I like LaTeX and behind these jobs there is a lot of LaTeX code.
> But Org gives me a much more light and productive workflow, allowing me
> to work at two levels.
> The main advantages that I see for this workflow with Org/Org-Publish
> 1. Lightness: LaTeX is too verbose.
> 2. Control of the composition process at various points. One of the
> qualities of LuaTeX is the possibility to control TeX primitives
> through scripts in Lua, and to act at various points in the pre- or
> post-process. But I have realized that with the happy fusion of Elisp
> and Org we can be much more precise and "surgical" ;-). Here,
> Org/LaTeX is much more powerful than LuaLaTeX.
> 3. Org's synaptic and org-anizational ability to control and manage the
> entire process of the creation of a book, from when the originals are
> received until everything is prepared to send to the printer.
> 4. An unique origin. The book can be produced on paper from a single
> source, but you can also export, from that source consistently, to
> other formats (HTML or Epub).
> Best regards,
> Juan Manuel
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2021-03-07 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 19:34 Juan Manuel Macías
2021-03-07 9:17 ` M. ‘quintus’ Gülker
2021-03-07 15:57 ` Juan Manuel Macías
2021-03-07 12:08 ` Diego Zamboni
2021-03-07 13:15 ` Vikas Rawal
2021-03-07 14:35 ` Colin Baxter
2021-03-07 16:03 ` Juan Manuel Macías
2021-03-08 10:46 ` Jonathan McHugh
2021-03-07 17:46 ` Dr. Arne Babenhauserheide [this message]
2021-03-07 18:30 ` Juan Manuel Macías
[not found] ` <email@example.com>
2021-03-07 20:20 ` Juan Manuel Macías
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 \
* 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).