From: Emmanuel Charpentier <emm.charpentier@free.fr>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Slight problems with links
Date: Mon, 29 Apr 2019 09:35:50 +0200 [thread overview]
Message-ID: <da77b94e76747367e4dc0e953a9f08914108a15b.camel@free.fr> (raw)
Dear list,
one of my uses od org-mode is to prepare documents wrapping R (and
sometimes Sagemath) call results in interpretation text. My reference
output is .pdf documents, but I *have* to prepare a .docx version (for
use in managerial spheres, where computer literacy is *very* low.
Cross-references and citations are a sine qua non, maths are useful.
I have been annoyed by a couple of deficiencies and inconsistencies
between exporters, so I prepared a test document testing various cases.
This documents and some exports are too big to be atached but can be
downloaded from
https://drive.google.com/open?id=1T6N_-WwphlnL2mB4f6BgX0u1K5mLnz4i (NE
= Native exporter, PE= ox-pandoc exporter).
TL;DR :
* I tested the built-in latex/pdf exporter as well as ox-pandoc, the
latter both for .pdf and .docx export. The built-in ODT exporter
doesn't export citations ; therefore, I didn't test it further.
* org-ref's :labels and :refs do not export to anything but the
built-in latex exporter. The native system of #+NAME:s and #+CAPTION:s,
a bit on the heavy side, seems not to fail (except that they do not
expand in a caption...).
* Maths, tables, figures are unproblematic.
* The requirements of org-reftex, the built-in latex exporter and ox-
pandoc being mutually incompatible, and some ingenuity is required. see
the org source. Org-ref's requirements do not simplify the
situation...
* Code snippets (i. e. source blocks exporting code) have a
captioning/numbering problem :
- With the built-in latex exporter, they are numbered and labeled
as figures.
- The pandoc latex exporter numbers them separately (as seen by
referencing them), but do not output this number (nor the category)
before the caption.
- The pandoc .docx exporter works as advertised.
So I have a couple of questions:
* What can be done to reconcile org-ref's, latex-exporter's and ox-
pandoc's requirements for bibliographies ?
* How to fix the pdf exporters' quirks with code snippets ?
HTH,
--
Emmanuel Charpentier
next reply other threads:[~2019-04-29 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 7:35 Emmanuel Charpentier [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-29 6:33 Slight problems with links Emmanuel Charpentier
2019-04-29 20:57 ` John Kitchin
2019-04-29 21:18 ` Emmanuel Charpentier
2019-04-29 21:23 ` John Kitchin
2019-04-29 21:48 ` Emmanuel Charpentier
2019-04-30 6:43 ` Ken Mankoff
2019-04-30 7:45 ` Emmanuel Charpentier
2019-04-30 18:11 ` John Kitchin
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=da77b94e76747367e4dc0e953a9f08914108a15b.camel@free.fr \
--to=emm.charpentier@free.fr \
--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).