From: William Denton <wtd@pobox.com>
To: Ypo <ypuntot@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: About exporting
Date: Mon, 29 Mar 2021 16:15:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2103291558290.18818@shell3.miskatonic.org> (raw)
In-Reply-To: <88a3facd-2f95-42b7-135a-d2ec6a730ba7@gmail.com>
On 29 March 2021, Ypo wrote:
> How do you think I should spend some hundreds (or thousands) of hours to
> achieve maestry exporting my documents?
I think the key question is: Do you want to preserve them as web pages or
page-based documents? If the web, then it's HTML; if documents, I'd use LaTeX.
OpenDocument is a fine format, and if you have a lot of fairly simple documents,
you could certainly use it, but it's not the best way to get articles and books
print-ready yourself. And if you want to make beautiful documents with great
typography, LaTeX is the best choice, and of course integrates very well with
Org. (I've never tweaked the LaTeX output from Org by hand, but some projects I
do fully in LaTeX because it's just easiest to have total control and edit with
AucTeX).
To get better at it, I'd recommend reading the manual for the Memoir class [1]
(the first few chapters that talk about page design, at least, then refer to the
rest as needed) and Robert Bringhurst's THE ELEMENTS OF TYPOGRAPHIC STYLE [2]
(which will give you ideas you can implement and right away your documents will
look great).
Bill
[1] https://www.ctan.org/pkg/memoir
[2] https://en.wikipedia.org/wiki/The_Elements_of_Typographic_Style
--
William Denton :: Toronto, Canada --- Listening to Art: https://listeningtoart.org/
https://www.miskatonic.org/ --- GHG.EARTH: https://ghg.earth/
Caveat lector. --- STAPLR: https://staplr.org/
next prev parent reply other threads:[~2021-03-29 20:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.51.1617033608.26133.emacs-orgmode@gnu.org>
2021-03-29 19:37 ` About exporting Ypo
2021-03-29 20:15 ` William Denton [this message]
2021-03-29 20:46 ` autofrettage
2021-03-29 21:39 ` Samuel Wales
2021-03-29 21:31 ` Juan Manuel Macías
2021-03-29 22:06 ` Tim Cross
2021-03-30 6:17 ` Eric S Fraga
2021-03-30 8:01 ` Colin Baxter
2021-03-30 8:13 ` Detlef Steuer
2021-03-30 10:15 ` Eric S Fraga
2021-03-30 11:40 ` Joost Kremers
2021-03-30 8:17 ` Eric S Fraga
2021-03-30 11:04 ` Juan Manuel Macías
2021-03-29 22:26 ` Thomas S. Dye
2021-03-30 4:47 ` Greg Minshall
2021-03-30 11:54 ` Martin Steffen
2021-03-30 12:44 ` autofrettage
2021-03-30 14:35 ` Martin Steffen
2021-03-30 14:44 ` autofrettage
2021-03-30 15:44 ` Juan Manuel Macías
2021-03-31 9:59 ` Eric S Fraga
2021-03-31 18:28 ` Martin Steffen
2021-04-01 6:52 ` Eric S Fraga
2021-04-01 7:00 ` Tim Cross
2021-04-01 7:29 ` Eric S Fraga
2021-04-01 8:50 ` Timothy
2021-04-01 11:33 ` Eric S Fraga
2021-04-01 13:25 ` Timothy
2021-04-02 14:06 ` Eric S Fraga
2021-04-01 14:21 ` Juan Manuel Macías
2021-03-30 20:49 ` Tim Cross
2021-03-31 18:56 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=alpine.DEB.2.22.394.2103291558290.18818@shell3.miskatonic.org \
--to=wtd@pobox.com \
--cc=emacs-orgmode@gnu.org \
--cc=ypuntot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).