From: Alex Fenton <email@example.com>
Subject: Ox-pandoc and Org-cite
Date: Thu, 14 Oct 2021 11:41:01 +0200 [thread overview]
Message-ID: <9217E511-2D99-420D-AA9A-1441955DA8E4@pressure.to> (raw)
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
I have recently forked  and tidied up ox-pandoc with some fixes for incompatibilities that had arisen with newer versions of pandoc. I'm talking to MELPA people about getting this distributed.
Briefly, ox-pandoc exports an .org file to a temporary .org (so that e.g. Babel code is resolved) and then calls pandoc to export to any of its many supported formats.
The arrival of citation support in Org is fantastic, but it is a bit tricky for ox-pandoc, b/c pandoc itself has csl-based cite processing ability. I'd appreciate any pointers on a couple of points:
1) how best to handle an file level option (BIBLIOGRAPHY) that is defined in a mode and in some (>9.4) versions of org itself? At the moment it's choking on incompatible types with 9.5, because ox-pandoc expects a string but gets a list.
2) how best to allow users to pick between org citation export, pandoc citeproc or letting biblatex do something? At the moment, there seems no way to prevent citation export (passthrough) or a filter mechanism.
Should I plan to write a org cite export handler that converts to a format that pandoc understands (the new Org citation format is not yet fully supported, though an issue  is filed)?
[-- Attachment #2: Type: text/html, Size: 1521 bytes --]
next reply other threads:[~2021-10-14 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 9:41 Alex Fenton [this message]
2021-10-14 18:57 ` Ox-pandoc and Org-cite M. ‘quintus’ Gülker
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 \
* 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).