From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: modify citation links in a derived HTML backend
Date: Sun, 4 Jul 2021 14:56:18 +0200 [thread overview]
Message-ID: <87h7haw83x.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <CAN_Dec8UembfTARoOchXVzqEgmUv0sz+HHS-50ObX+-+MCx8Dw@mail.gmail.com> (Matt Price's message of "Sat, 3 Jul 2021 17:32:50 -0400")
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On 2021-07-03, Matt Price wrote:
> I've added some comments in the issue you linked to, but in the meantime
> I've also come up with what seems to be at least a semi-viable hack for
> adding native CSL citation support to org-re-reveal. It involves creating
> two new variables and then let-setting `citeproc-fmt--formatters-alist` in
> `org-re-reveal-export-to-html`. Something similar could presumably be done
> in other derived backends.
>
> I find it quite hackish and I don't know whether perhaps some more general
> solution could be found, but in any case here is the code, which I have
> inserted into org-re-reveal.el locally:
Thank you for sharing your code, Matt!
What is the general state of this new citation handling with respect
to export backends? Did you create the settings for HTML from
scratch or did you take inspiration from HTML export functionality?
I guess that basic support should go into ox-html, while small
modifications could than take care of specifics for reveal.js
presentations...
Best wishes
Jens
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5290 bytes --]
next prev parent reply other threads:[~2021-07-04 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 17:53 modify citation links in a derived HTML backend Matt Price
2021-07-03 7:53 ` Jens Lechtenboerger
2021-07-03 21:32 ` Matt Price
2021-07-04 12:56 ` Jens Lechtenboerger [this message]
2021-07-04 16:12 ` Matt Price
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7haw83x.fsf@wi.uni-muenster.de \
--to=lechten@wi.uni-muenster.de \
--cc=emacs-orgmode@gnu.org \
--cc=moptop99@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.