From: "Bruce D'Arcus" <firstname.lastname@example.org>
To: John Kitchin <email@example.com>
Cc: Vikas Rawal <firstname.lastname@example.org>,
Subject: Re: [oc] provide style/citation preview?
Date: Fri, 25 Mar 2022 13:48:58 -0400 [thread overview]
Message-ID: <CAF-FPGNPf9=HHK9FxZ0-92xGqxtouGWGZdNBcVDVms-qrTDiTQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
On Fri, Mar 25, 2022 at 8:55 AM John Kitchin <email@example.com>
> I think this kind of preview is well-suited for external packages.
You may be right.
> There is a subtle point I ran into with this preview approach though,
> and that is what is the backend export you want to see? People expect
> one source (org) to export to different backends, and even use one
> source to make a PDF and HTML (and maybe others). Now it also possible
> to use different citation styles for different backends, and the
> backends may use different citation processors (e.g. bib(la)tex or CSL).
> I felt this was too complex to try to get right in one package. External
> packages could provide any subset of these they want, e.g. the way
> https://github.com/andras-simonyi/org-cite-csl-activate does. My opinion
> of course.
oc-csl-activate uses org-cite-csl--fallback-style-file for the preview
style, but also has a org-cite-csl-activate-use-document-style defcustom to
optionally override that. A LaTeX preview wouldn't need this.
Seems more generally a user would need to be able to specify what the
export target is.
But I guess per your point, one could do configuration by simply selecting
whatever preferred activate processor. So, for example, we could have one
for latex preview.
> I think the basic CSL styled citation tooltip that is independent of the
> final state is a good compromise. The point is to give enough context
> about the key to tell you what it is without visiting the source, and if
> you need more, you go visit the source (bibtex file, org file, etc.).
[-- Attachment #2: Type: text/html, Size: 2056 bytes --]
prev parent reply other threads:[~2022-03-25 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 13:46 Bruce D'Arcus
[not found] ` <CALtzAB3Wh9dp_5ik3wN5JA2WmYb-cOoJ7AEKKkUfTXRuKC_5qQ@mail.gmail.com>
2022-03-24 16:32 ` Fwd: " Vikas Rawal
2022-03-24 16:49 ` Bruce D'Arcus
2022-03-24 23:25 ` Vikas Rawal
2022-03-25 12:43 ` John Kitchin
2022-03-25 17:48 ` Bruce D'Arcus [this message]
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).