emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Diego Zamboni <diego@zzamboni.org>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org as a book publisher
Date: Sun, 07 Mar 2021 17:03:42 +0100	[thread overview]
Message-ID: <87eegrq7c1.fsf@posteo.net> (raw)
In-Reply-To: <CAGY83EfGcuKV6rfMhK_a+9oUNtPnZza-722dHKwCoVxouq_ebw@mail.gmail.com> (Diego Zamboni's message of "Sun, 7 Mar 2021 13:08:20 +0100")

Hi Diego,

Thank you very much for your comments.

Diego Zamboni <diego@zzamboni.org> writes:

> 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 Totally agree. Leslie Lamport originally created LaTeX (as far as I
know) as a simplified way of handling TeX for his own documents, since
the other format of TeX, plainTeX, was quite spartan. Then LaTeX has
grown incredibly thanks to its extensibility qualities: a small kernel
(unlike ConTeXt, which is more monolithic) and a ecosystem of macro
packages. If we make an analogy with the old days of mechanical
printing, I always say that TeX is the typographer, the one who gets his
hands dirty with ink, while LaTeX wears a tie and is in the editorial
design department. TeX works on the merely physical plane, and he is
only interested in how each element on the page is positioned in
relation to other elements. Here the minimum indivisible element would
be the letter, which to TeX's eyes is a box with certain dimensions.
LaTeX lives more on a semantic plane: for LaTeX there is no lines or
letters or paragraphs, but rather headings, heading levels, lists,
quotes, verses, chapters, tables, equations, tables of contents... But,
as you say, in LaTeX you can still see too many gears. With Org we can
work on a lighter and cleaner document. And with a single source for
multiple formats!

Before moving to Org, I applied this `philosophy' to the markdown/pandoc
tandem. But since I migrated to Emacs/Org a few years ago, it's almost
like having superpowers :-D

Best regards,

Juan Manuel 

  parent reply	other threads:[~2021-03-07 16:04 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 [this message]
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] ` <87ft16hn62.fsf@emailmessageidheader.nil>
2021-03-07 20:20   ` Juan Manuel Macías

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=87eegrq7c1.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=diego@zzamboni.org \
    --cc=emacs-orgmode@gnu.org \


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