public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Thomas J.' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Citeproc/Order of filters being called
Date: Wed, 29 Nov 2023 05:28:37 -0800 (PST)	[thread overview]
Message-ID: <15e09292-83a1-4e28-ba84-d0c518be709dn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1265 bytes --]

Hi everyone,

Since pandoc-fignos isn't working anymore (at least, with my Pandoc 
version), I have written a Lua filter that basically does what fignos does, 
namely replacing tags such as @fig:fig1 with anchors/refs to the figures in 
html/latex. Now, if I am trying to use this filter without citeproc, 
everthing works as expected. The moment I use --citeproc, I get the error 
message "fig:fig1 citation not found" and I have no link in my output file. 
I am actually calling the lua filter BEFORE --citeproc in the command 
line... 

pandoc --lua-filter=filter/pandoc-figref.lua --citeproc --number-sections 
--from markdown --template=templates/phimisci-1-5.html --bibliography=
$BIBLIOGRAPHY --csl=csl/apa7-single-spaced.csl yaml/gen-metadata.yaml 
article/$1 article/$2 -o $HTMLFILE

What am I missing? Thanks for the help!

Best wishes,
Thomas

-- 
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/15e09292-83a1-4e28-ba84-d0c518be709dn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2651 bytes --]

             reply	other threads:[~2023-11-29 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 13:28 'Thomas J.' via pandoc-discuss [this message]
     [not found] ` <15e09292-83a1-4e28-ba84-d0c518be709dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-29 14:49   ` 'William Lupton' via pandoc-discuss
     [not found]     ` <CAEe_xxid8YRTLJKC=8jvD2ps4a7YoQe=ZS3DMMt0VJ3d0e-04Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-29 18:29       ` 'Thomas J.' via pandoc-discuss
     [not found]         ` <ee97eefb-cb70-4bf9-859c-e75448438894n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-30  9:56           ` 'Thomas J.' via pandoc-discuss

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=15e09292-83a1-4e28-ba84-d0c518be709dn@googlegroups.com \
    --to=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).