From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/30584 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: John Carter Wood Newsgroups: gmane.text.pandoc Subject: Re: Divergent styling when using CSL in pandoc(?) Date: Fri, 20 May 2022 04:32:46 -0700 (PDT) Message-ID: <7eba7c69-7dae-4f82-92ac-6e98b3bcb639n@googlegroups.com> References: <0daa1a20-d847-47f5-a465-708c7875ff8an@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1712_953532215.1653046366496" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17776"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCYPBGVKTEEBBYHYTWKAMGQEBCLDZ3Q-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Fri May 20 13:32:52 2022 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-oi1-f191.google.com ([209.85.167.191]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ns0sF-0004QW-Mf for gtp-pandoc-discuss@m.gmane-mx.org; Fri, 20 May 2022 13:32:51 +0200 Original-Received: by mail-oi1-f191.google.com with SMTP id ay32-20020a056808302000b002f96abff093sf3813535oib.23 for ; Fri, 20 May 2022 04:32:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=D0cScWrpwBpC+RnJ9TQ+dMqaN6da3MfGVBjCF0ibbpc=; b=NC9/iokjkm/EoCIRp+iqAF36w8O+plmnoJjnnmnX3mwF0buVwj7WA4UQuZibk26oVq 3kw9tShO7/YzQ1za7mjhlf4EP15TodDS9nQrR8GkByhx2nh2T85OnMeIaLFLZVan3lBk gsHAMRncU76Kf7iYiFmcA57oHJauxTQvWHqLlAmmZlA/Ti6fSBQezbUb221GJqUGYZSk Ep4/ZUfz5ST70+yd75QJrNq8qjr2ogv/vKU2viAdxaNYQFp2LRwvsaFR0eaOVSBgh27M 3/ACVIOB92ilNdwQrFQfYuoIdsgjG/UTQn0+GsYR5CYtSkpeKWW8GG2vcf1YAuSaOkHR BklQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=D0cScWrpwBpC+RnJ9TQ+dMqaN6da3MfGVBjCF0ibbpc=; b=77nS+n6N83gTetXnYyK2/rQPYVizvjpiB1+Qek+ts9z+hVTVF4WG+uKjBzS6gyaqOU hkysnq9oyEviu3YWoa8d1CnoY74R+MerdX64yLDn488XMwQKdBfHTIoF5P+OOKRdIIwm QAPpoG3F4ZisBNH2TmOxYgwmNVDv/y6uM7IDkjbX2EOUBWfuMWRNzJ876rTDy6HklMHZ IMg7tMyU1Jx07Pw7KRd1gM5tyaqtRNqGRfbV/dRJVwkeLQJuHAtpPdA8J1ZabGWagPyn UG9D/yKq8s7QVxKtpox7qopPMXf/XWR/l6BV42gqVnIPZm4D/o24YvD97pn0Oc4kiKDn u8Yg== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AOAM531av74+dixjsWpRQDjfMeu+92GFt5yweYco8IGiGMcdHGsSF+YO H7mhtu3wze4I2NPorBAW7+c= X-Google-Smtp-Source: ABdhPJxTBrBlQJ2aN/tXM9abkAR/MM/qvev6r8SNkv++YIGWSbhdXTzWm/332BjoF0XpR2vrPfHT7A== X-Received: by 2002:a05:6870:89a8:b0:f1:97d2:931a with SMTP id f40-20020a05687089a800b000f197d2931amr5777281oaq.82.1653046370664; Fri, 20 May 2022 04:32:50 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a05:6808:4cc:b0:32b:a70:4ae2 with SMTP id a12-20020a05680804cc00b0032b0a704ae2ls64343oie.4.gmail; Fri, 20 May 2022 04:32:48 -0700 (PDT) X-Received: by 2002:a05:6808:218c:b0:326:955e:f39 with SMTP id be12-20020a056808218c00b00326955e0f39mr5112740oib.237.1653046367140; Fri, 20 May 2022 04:32:47 -0700 (PDT) In-Reply-To: <0daa1a20-d847-47f5-a465-708c7875ff8an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> X-Original-Sender: woodjo-ZOsAvrTRSvuEhhMi0yms2Q@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:30584 Archived-At: ------=_Part_1712_953532215.1653046366496 Content-Type: multipart/alternative; boundary="----=_Part_1713_1248311428.1653046366496" ------=_Part_1713_1248311428.1653046366496 Content-Type: text/plain; charset="UTF-8" I didn't really make clear enough in the original post: with pandoc in these cases I'm going from Markdown to docx. Sorry. John Carter Wood schrieb am Freitag, 20. Mai 2022 um 13:00:49 UTC+2: > 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/7eba7c69-7dae-4f82-92ac-6e98b3bcb639n%40googlegroups.com. ------=_Part_1713_1248311428.1653046366496 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I didn't really make clear enough in the original post: with pandoc in thes= e cases I'm going from Markdown to docx. Sorry.

John Carter Wood schrieb am = Freitag, 20. Mai 2022 um 13:00:49 UTC+2:
I have been working on creating a CSL style for= the publication house-style at my institution: I've been making progre= ss adapting another style but am running into a few issues that seem to onl= y 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 conn= ector 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<= br>
There are a few issues, but the format for items in collections seem= s to be the main one.

Here is a screenshot of the same citation: th= e one on top (which formats incorrectly) was created by using pandoc. The o= ne on the bottom (which formats correctly) was directly inserted into the d= ocument using Zotero's functionality in LibreOffice.
3D"CS=

The problems:
1. et al. is capit= alising
2. (ed.) is capitalising
3. the p./pp. contextu= alisation isn't working right: using pandoc, when the locator is a sing= le 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 pag= e, then "pp." appears in both, as it should.

<= /div>
As I said, when looking at style using the example citations in t= he visual editor at for CSL (https://editor.citationstyles.org/visualEditor/), it also looks right (as in the second cite.)


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 wo= rkflow, 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):

ht= tps://pastebin.com/xefmukzw

Thanks in advance = for any help.

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d= /msgid/pandoc-discuss/7eba7c69-7dae-4f82-92ac-6e98b3bcb639n%40googlegroups.= com.
------=_Part_1713_1248311428.1653046366496-- ------=_Part_1712_953532215.1653046366496--