From: Diego Zamboni <email@example.com>
To: "Juan Manuel Macías" <firstname.lastname@example.org>
Cc: orgmode <email@example.com>
Subject: Re: Org as a book publisher
Date: Sun, 7 Mar 2021 13:08:20 +0100 [thread overview]
Message-ID: <CAGY83EfGcuKV6rfMhK_a+9oUNtPnZza-722dHKwCoVxouq_ebw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2962 bytes --]
Hi Juan Manuel,
Thanks for sharing this - the output looks very nice.
I think with Org and a setup like you describe, we are one step closer to
separating content (what) from form (how) in a document. This was one of
the original goals of LaTeX, but of course in a LaTeX document much of the
"how" is still visible through the "what". With Org the separation becomes
clearer, by hiding the LaTeX structures (almost) completely, and by
allowing to produce multiple formats from the same source document.
I have done something similar with my books, which I publish through
Leanpub. I keep the source of each book in Org, and from there the exporter
takes care of producing the Leanpub markup and format, which in turn takes
care of converting it to PDF, ePub or other formats.
On Sat, Mar 6, 2021 at 8:35 PM Juan Manuel Macías <firstname.lastname@example.org>
> 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
[-- Attachment #2: Type: text/html, Size: 3585 bytes --]
next prev parent reply other threads:[~2021-03-07 12:10 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 [this message]
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
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).