From: "Thomas S. Dye" <tsd@tsdye.online>
To: emacs-orgmode@gnu.org
Subject: Re: About exporting
Date: Mon, 29 Mar 2021 12:26:44 -1000 [thread overview]
Message-ID: <87y2e5ppej.fsf@tsdye.online> (raw)
In-Reply-To: <88a3facd-2f95-42b7-135a-d2ec6a730ba7@gmail.com>
Aloha Ypo,
"Exporting for life" is a vague target, so it is difficult to give
precise recommendations.
It is usually the case that export to LaTeX doesn't require
subsequent modification of the tex file. In most cases for my
work, I am exporting to a LaTeX document style/class provided by
someone else. This is fairly typical of the LaTeX world, where
academic journals and university degree programs design their own
in-house styles and then ask authors to use them. The idea behind
LaTeX is that LaTeX defines the meaningful units of a document
(headers, paragraphs, quotes, etc.) so that a single LaTeX
document can be exported to multiple targets, each of which styles
the document units in its own way. Because Org mode targets
LaTeX, and not a particular style, this means that Org mode
inherits LaTeX's style agnosticism.
Of course, there are exceptions to this general rule, where a
LaTeX class/style defines document units that extend the LaTeX
spec. It can be tricky to get Org mode to export to one of these
non-standard styles.
If you intend to create documents with bibliographies, then IMHO
LaTeX export is the best choice. BibTeX defines a plain text
bibliographic database that is very widely used and capable of
meeting the most exact bibliographic requirements. John Kitchin
has written org-ref to manage BibTeX databases from Org mode, and
Joost Kremers has ebib, which integrates nicely with Org mode and
accomplishes many of the same tasks covered by org-ref. A native
Org mode bibliographic solution has been discussed for many years
and there is an org-cite branch that is a nearly complete work in
progress. This will be designed to use Citation Style Language,
rather than BibTeX, which means (at least currently IIUC) that
there will be somewhat less fine control over bibliographic
format, although there are thousands of CSL style definitions,
which presumably cover all the most likely targets. In my
experience, CSL approximates most bibliographic styles, rather
than producing them exactly, so YMMV.
Even without the need for bibliographies, LaTeX might be your best
choice. In my field, most of the journals *require* an MS Word
document, a practice that gives me no end of heartburn. I've
found that export to LaTeX followed by conversion with the Haskell
program pandoc gives the best results. Pandoc is pretty nifty,
with conversion among quite a few different formats. LaTeX
provides a rich input, which pandoc handles really well.
hth,
Tom
Ypo writes:
> Hi
>
> After some years of using orgmode, and exporting using its
> defaults, I would
> like to take a quality leap and find a way of exporting for
> life. My options:
> LaTeX, ODT, HTML.
>
> LaTeX: I can see some masters here that make professional books,
> and I have some
> friends that publish scientific papers using LaTeX. But, it
> looks like a like a
> rabbit hole to me, since even the masters seem to have to modify
> the tex file
> directly (is this correct?), not being sufficient orgmode to
> culminate the work
> by itself. And to learn LaTeX seems a lifelong activity (almost
> like "learning"
> orgmode). BTW, when I export to LaTeX although it gets the job
> done, it sends a
> lot of error messages.
>
> ODT: I take this one as a lower level solution than LaTeX, but
> it looks easier
> to tame, and it even allows to use templates, for example to
> make reports in
> the workplace. Do you think it is worth focusing on ODT
> exporting? Could it be a
> definitive solution to publish papers and books directly from
> orgmode? ODT
> exporting sends some error message to me, but at least I
> understand it.
>
> HTML: I have seen some themes
> <https://olmon.gitlab.io/org-themes/latexcss/latexcss.html>
> designed to export
> in LaTeX format using HTML. Here we would have the "definitive
> tool": The power
> of LaTeX in the versatility that could give the use of different
> themes for
> different purposes. But, do you think it could get, some day,
> the quality of a
> direct LaTeX export? No errors by my side when exporting to
> HTML.
>
> How do you think I should spend some hundreds (or thousands) of
> hours to achieve
> maestry exporting my documents?
>
> Best regards.
--
Thomas S. Dye
https://tsdye.online/tsdye
next prev parent reply other threads:[~2021-03-29 22:27 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
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 [this message]
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=87y2e5ppej.fsf@tsdye.online \
--to=tsd@tsdye.online \
--cc=emacs-orgmode@gnu.org \
/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).