Bastien Dumont schrieb am Freitag, 20. Mai 2022 um 15:42:47 UTC+2:

When testing your CSL file, you should be aware that Zotero and (I guess) the Visual Editor rely on citeproc-js, which is not fully compliant with the CSL specification. Sometimes, Pandoc is right against them. For instance, if I remember well, the default value for the "match" attribute is "any" in citeproc-js, although it should be "all" (as it is in Pandoc). On the other hand, the specification does not define the expected behaviour for all cases. The issue documented by your first screenshot is a good example of that. The "title" macro is called on l. 332 with the attribute text-case="title", but the <text> element on l. 117 included in this macro has text-case="lowercase": which one should have the precedence? Unless I have missed something, the CSL specification does not define that, so Pandoc applies the attribute value set on the upper-most element and citeproc-js that of the inner-most element. Neither is wrong, so the only solution is to avoid such conflicts in your stylesheet (e.g. by removing the attribute on l. 332).

As for the issue with "p./pp.", I guess that the problem is in your Markdown input, but I can't be sure. Could you provide a minimal sample MD file with a stylesheet and a bibliography?

Le Friday 20 May 2022 à 04:00:49AM, John Carter Wood a écrit :
> I have been working on creating a CSL style for the publication house-style at
> my institution: I've been making progress adapting another style but am running
> into a few issues that seem to only crop up when using the CSL during a
> document transformation with pandoc (version 2.18, with CSL file specified in a
> YAML block). In the preview for the visual editor they look OK and when I
> insert them via Zotero's connector into a LibreOffice / Word document they look
> fine too; however, when I create the docx via pandoc there are unwanted
> variations on a few points
>
> There are a few issues, but the format for items in collections seems to be the
> main one.
>
> Here is a screenshot of the same citation: the one on top (which formats
> incorrectly) was created by using pandoc. The one on the bottom (which formats
> correctly) was directly inserted into the document using Zotero's functionality
> in LibreOffice.
> CSL-pandoc-issues.png
>
> The problems:
> 1. et al. is capitalising
> 2. (ed.) is capitalising
> 3. the p./pp. contextualisation isn't working right: using pandoc, when the
> locator is a single page, *the page range for the whole citation* revert to a
> single "p.", even when it should be plural; if the locator is more than one
> page, then "pp." appears in both, as it should.
>
> As I said, when looking at style using the example citations in the visual
> editor at for CSL (https://editor.citationstyles.org/visualEditor/), it also
> looks right (as in the second cite.)
>
> CSL-IEG-Visual-Editor.png
>
> I am running into a few other challenges with working out CSL, but since this
> one seems to specifically relate to using pandoc (which is my main workflow, as
> I write in Markdown), I thought I would ask here whether this is a known issue,
> whether I'm doing something wrong and whether there's a way to solve this.
>
> Here, for reference, is my CSL file (which is still a work in progress):
>
> https://pastebin.com/xefmukzw
>
> Thanks in advance for any help.
>
> --
> 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 [1]pandoc-discus...@googlegroups.com.
> To view this discussion on the web visit [2]https://groups.google.com/d/msgid/
> pandoc-discuss/0daa1a20-d847-47f5-a465-708c7875ff8an%40googlegroups.com.
>
> References:
>
> [1] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [2] https://groups.google.com/d/msgid/pandoc-discuss/0daa1a20-d847-47f5-a465-708c7875ff8an%40googlegroups.com?utm_medium=email&utm_source=footer