public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Denis Maier <denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Manipulate CSL bibliography before processing
Date: Wed, 16 Sep 2020 17:29:50 +0200	[thread overview]
Message-ID: <54c0b3a9-f742-18e4-9fc2-8a3b7f2f3632@mailbox.org> (raw)

Hi,

is it possible to manipulate a CSL bibliography before Pandoc processes 
the citations?
Let's say I have one huge database, and I want to do ad hoc 
modifications, for example add a certain field to a couple of entries.

The specific use case would be this:
You write an essay about Kant, and you want to use the usual 
abbreviations (KrV, KpV, etc.), but you don't want to have those 
abbreviations in your main database. In  your metadata you could have 
something like this:

```
bibliography: bib.json
bibliography-modifications:
   - id: kant-id1
     add:
       - field: citation-label
         content: KrV
```

Of course, you can always implement this with some sort of 
pre-processing, e.g. with a python script. But a pandoc solution would 
be neat.

Is the content of the bibliography file exposed to the filter 
architecture before citeproc actually processes the bibliography?

Best,
Denis

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/54c0b3a9-f742-18e4-9fc2-8a3b7f2f3632%40mailbox.org.


             reply	other threads:[~2020-09-16 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 15:29 Denis Maier [this message]
     [not found] ` <54c0b3a9-f742-18e4-9fc2-8a3b7f2f3632-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-17  9:58   ` Albert Krewinkel
     [not found]     ` <87mu1on2qt.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-17 10:19       ` Albert Krewinkel
     [not found]         ` <87k0wsn1sw.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-17 11:07           ` Denis Maier
2020-09-17 17:59   ` John MacFarlane
     [not found]     ` <m2y2l8i8so.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-17 18:59       ` Denis Maier
     [not found]         ` <9af493a5-336d-a726-4266-b89104f0cebc-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-17 21:37           ` John MacFarlane
     [not found]             ` <m2363gw0cv.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-18  6:32               ` Denis Maier
     [not found]                 ` <a5b830a3-fed0-1024-cf80-d878b1514bb9-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-18  7:50                   ` Denis Maier

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=54c0b3a9-f742-18e4-9fc2-8a3b7f2f3632@mailbox.org \
    --to=denis.maier.lists-cl+vpiynx/1afugrpc6u6w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).