From: Emmanuel Charpentier <emm.charpentier@free.fr>
To: joseph.vidal.rosset@gmail.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-mode vs pandoc export
Date: Fri, 27 Sep 2019 07:13:27 +0200 [thread overview]
Message-ID: <966cb1982dd484f5b1cf813ff3bc82e22a51627c.camel@free.fr> (raw)
In-Reply-To: CAD-VTcHvr6thPe+9FSCfC94s-8j8F7rSXyvxiZbo9cyaarZCLg@mail.gmail.com
I suppose that you need org-mode to use Babel features (code and/or
code execution results intermixed with your paper's text).
I have had trouble with .dot exporting using the builtin .dot exporter,
but can't, for the life of me, remembering if my troubles were cross-
reference or citations-related (an academic paper usually needs
both...). I noted that the references done via John Kitchin's excellent
org-ref didn't export to .dot.
As far as I can tell, ox-pandoc does its own numbering (generating an
intermediate temporary file that I never managed to catch) and does not
use pandoc-crossref.
ISTR that a "clever" use of org-ref allows to number equations... in
LaTeX output. I also STR that it doesn't work in .docx output. John
Kitchin (the org-ref author) thinks that the key is to generate a
correct \LaTeX file and to export that to .docx via pandoc.
At this point, writing a \LaTeX file with pandoc export in mind is
probably your best bet. There exist (limited) alternatives to the
Babel features of org-mode:
- knitr (supports R and Python code in "session"mode, i. e. continuity
between code chunks),
- SageTeX (post-processing in a single Sagemath run ; can include code
for a variety of math software, including R),
- Pythontex (postprocessor, supports Python, Sage, Octave and a couple
other, but not R ; a clever use of knitr and Pythontex is possible).
Possible alternative: Markdown + Codebraid (supports a hanful of
langiages, including R and (development branch) Sage). This should
accept pandoc-crossref numbering. But it's Markdown, with limited
formatting abilities...
So, we have an array of partial solutions, none universal. Pick your
poison...
Out of curiosity: in which domain still exist journal publishers not
accepting \LaTeX ? I suspect medicine...
HTH,
--
Emmanuel Charpentier
next reply other threads:[~2019-09-27 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 5:13 Emmanuel Charpentier [this message]
2019-09-27 6:19 ` org-mode vs pandoc export Joseph Vidal-Rosset
-- strict thread matches above, loose matches on Subject: below --
2019-09-27 12:36 CHARPENTIER Emmanuel
2019-09-26 16:14 Joseph Vidal-Rosset
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=966cb1982dd484f5b1cf813ff3bc82e22a51627c.camel@free.fr \
--to=emm.charpentier@free.fr \
--cc=emacs-orgmode@gnu.org \
--cc=joseph.vidal.rosset@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).