public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: Separating multiple citations in generated footnote
Date: Mon, 30 May 2022 08:14:45 +0000	[thread overview]
Message-ID: <8ed092b504f248fa984c4284113f68ff@unibe.ch> (raw)
In-Reply-To: <baf8fe27-c662-4825-981d-b49fb7b38d71n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2993 bytes --]

I don’t have a particular suggestion for what you need, but I might be interested in what you already do. could you perhaps share your filters ?

Best,
Denis

Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von Shane Liesegang
Gesendet: Montag, 30. Mai 2022 09:07
An: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Betreff: Separating multiple citations in generated footnote

My institution has a few specific citation style requirements that stray from the standard Chicago Style. The changes are mostly around specific works, so it's difficult-to-impossible to meet the requirements by making a new CSL.

For the most part I'm able to handle it with Lua filters. I intercept the citation reference both before and after --citeproc runs and make whatever changes I need to; this might entail changing the style to SuppressAuthor, making some capitalization/punctuation changes, etc. In general this works well, but where it gets difficult is if a single Cite element contains multiple citations. In that case, looking at the generated footnote, there's no hard indicator of which portion came from which citation. I've got something working based on scanning for semicolons, but I worry that's a little bit fragile and will probably break on certain sets of reference data.

Is there any good way of mapping portions of the footnote to citation keys? I was thinking to wrap them in a span with some custom metadata, but I can only see the citations either before --citeproc (when the footnote doesn't exist yet) or after (when the multiple citations have already combined). What would be truly ideal would be the ability to filter the citation process itself, but I'm assuming since that's from a different library that it is not exposed to Lua?

Like I said, I have something mostly working now, but any thoughts/advice would be appreciated.
--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/baf8fe27-c662-4825-981d-b49fb7b38d71n%40googlegroups.com<https://groups.google.com/d/msgid/pandoc-discuss/baf8fe27-c662-4825-981d-b49fb7b38d71n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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/8ed092b504f248fa984c4284113f68ff%40unibe.ch.

[-- Attachment #2: Type: text/html, Size: 5645 bytes --]

  parent reply	other threads:[~2022-05-30  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  7:06 Shane Liesegang
     [not found] ` <baf8fe27-c662-4825-981d-b49fb7b38d71n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-30  8:14   ` denis.maier-NSENcxR/0n0 [this message]
     [not found]     ` <8ed092b504f248fa984c4284113f68ff-NSENcxR/0n0@public.gmane.org>
2022-05-30 13:42       ` Shane Liesegang
     [not found]         ` <CAD7-qeusumC9zcpbCGbjevJ6J9Vdi4W8YJyTjiTmbR_yk5+mrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-31  7:24           ` AW: " denis.maier-NSENcxR/0n0
     [not found]             ` <873d53586f8b4f968ac667b38da1796c-NSENcxR/0n0@public.gmane.org>
2022-05-31  8:29               ` Shane Liesegang
     [not found]                 ` <25193173-1E8E-4A2B-81C2-9AB3BBE6DC12-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-31  8:59                   ` Bastien DUMONT
2022-05-31 11:34                     ` BPJ
     [not found]                       ` <CADAJKhDwb6p9DxUrN-d5Rja6q6cteESc5MBRZBZwkh8dx5UwEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-31 11:43                         ` BPJ
     [not found]                           ` <CADAJKhCNRMrBE5erg3N2_vj-Y+W3=r-nwjDexzh89TnHTDrC4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-31 12:33                             ` Bastien DUMONT
2022-05-30 13:26   ` Albert Krewinkel
     [not found]     ` <87wne3cfem.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-05-31  7:08       ` Shane Liesegang
2022-06-01 17:36       ` jcr
     [not found]         ` <d07b4bcd-8431-4fff-8b61-4d482ae382bcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-01 18:43           ` AW: " denis.maier-NSENcxR/0n0

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=8ed092b504f248fa984c4284113f68ff@unibe.ch \
    --to=denis.maier-nsencxr/0n0@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).