public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John Carter Wood <woodjo-ZOsAvrTRSvuEhhMi0yms2Q@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Divergent styling when using CSL in pandoc(?)
Date: Fri, 20 May 2022 04:00:49 -0700 (PDT)	[thread overview]
Message-ID: <0daa1a20-d847-47f5-a465-708c7875ff8an@googlegroups.com> (raw)


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

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. 
[image: 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.)

[image: 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 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/0daa1a20-d847-47f5-a465-708c7875ff8an%40googlegroups.com.

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

[-- Attachment #2: CSL-pandoc-issues.png --]
[-- Type: image/png, Size: 39492 bytes --]

[-- Attachment #3: CSL-IEG-Visual-Editor.png --]
[-- Type: image/png, Size: 39430 bytes --]

             reply	other threads:[~2022-05-20 11:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHYbDjihMB6Uii56E23JjqNZrfiNK0npPkAgABzaCCAB6Z9gIAAY+Sw>
     [not found] ` <AQHYbDjihMB6Uii56E23JjqNZrfiNK0npPkAgABzaCA=>
2022-05-20 11:00   ` John Carter Wood [this message]
     [not found]     ` <0daa1a20-d847-47f5-a465-708c7875ff8an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-20 11:32       ` John Carter Wood
2022-05-20 13:42       ` Bastien DUMONT
2022-05-20 14:56         ` John Carter Wood
     [not found]           ` <e4cef3f2-bf3f-4359-87b7-61f9f3309670n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-20 15:50             ` Bastien DUMONT
2022-05-20 16:06               ` John Carter Wood
     [not found]                 ` <04626317-9c4b-4135-abfb-5ab0ae4909b5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-20 16:15                   ` Bastien DUMONT
2022-05-20 16:37                     ` John Carter Wood
2022-05-20 18:45         ` AW: " denis.maier-NSENcxR/0n0
     [not found]           ` <ae5227d7f2574c9ea33550a84d6e03e9-NSENcxR/0n0@public.gmane.org>
2022-05-25 17:25             ` John Carter Wood
     [not found]               ` <4217cb45-f6db-4b04-a598-20ac2422d02an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-25 21:36                 ` AW: " denis.maier-NSENcxR/0n0
     [not found]                   ` <727f6fde7695493c8d44da2ed2cb52b1-NSENcxR/0n0@public.gmane.org>
2022-05-26  7:18                     ` John Carter Wood

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=0daa1a20-d847-47f5-a465-708c7875ff8an@googlegroups.com \
    --to=woodjo-zosavrtrsvuehhmi0yms2q@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).