From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/30898 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.text.pandoc Subject: AW: Changing colons to full-stops in titles Date: Fri, 1 Jul 2022 16:16:56 +0000 Message-ID: References: <78df697a-50f5-46d0-b0b8-29a2cbc9509an@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_bc85a4891eec431f846ee69f9fcbe167unibech_" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20964"; mail-complaints-to="usenet@ciao.gmane.io" To: Original-X-From: pandoc-discuss+bncBCZ27W53TUFBB6537SKQMGQEGJV3DZA-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Fri Jul 01 18:17:04 2022 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-wr1-f59.google.com ([209.85.221.59]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o7JKI-00056J-Qq for gtp-pandoc-discuss@m.gmane-mx.org; Fri, 01 Jul 2022 18:17:02 +0200 Original-Received: by mail-wr1-f59.google.com with SMTP id e5-20020adff345000000b0021b9f00e882sf496500wrp.6 for ; Fri, 01 Jul 2022 09:17:02 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1656692222; cv=pass; d=google.com; s=arc-20160816; b=ymWkOL/Z8DfJf3GIbMf2z1ouE4WDGfMayAEU4aFOvGlSzXMz9+46CYJET2lEKgoSW6 OVbZxh1QFPoESBHszUYVPj6hcd0NWMq+Jxuu+62buCQVrysC7A31uxZ+x8oRiw4hWFfq O6fkjNQY11o88B0Sr46T1SIpyH5sZOviPMp8B7t0HrjfpR6ePmSrbZR6CFNI1wNi64Na +MrwDjVUBXPhuCHh5+PxaRDyhOQeC5X29pCAVDwTVEyNZwe5vlW7QaDUVZPiwFRqAZDT 2fvjsnA8RwnO4TVfbT7MMd7Xdr2EueW76vEm52tTindGsBkvK8BOBhVKYIKi3bVtnqj9 dCsg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:mime-version :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:to:from:sender :dkim-signature; bh=QQa8nCgA0gmxaAgGGbAMQPhN4+fGvJKPbGeFUybfyKk=; b=kiGa8HEziGvwUIiYl5OGCiee6GVhdilpUyPmWZtuWHdBGkCt4Ele36IOkuIeTvZ+jC lbW1N0B+QvM0COVMBAW/T+J64DgAmDHyhyCaedeFVfWk9nFD9QRVqG93l95MnN8qQzEO bSs7TWry4GZJ95w8I+5sldwt3mNz40V3tt4bsigh+sIG74RxyTgoKksiy/Fo1JsgTTZk KeLGeqo37Eh/1FvqfS46uk4nWqgdCZCJEdOv/x2u3LZYUgBAg+0vmW3xVUjB/7f8ep5z BgW7sfL5tZ8Kj8Eawf2Na47X92Ci9ZIk+om3Rz2tYg5Gde06sHzRrKOAUsbNHJUqP3U6 ka4Q== ARC-Authentication-Results: i=2; gmr-mx.google.com; spf=pass (google.com: domain of denis.maier-NSENcxR/0n0@public.gmane.org designates 130.92.0.83 as permitted sender) smtp.mailfrom=denis.maier-NSENcxR/0n0@public.gmane.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=unibe.ch DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=sender:from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=QQa8nCgA0gmxaAgGGbAMQPhN4+fGvJKPbGeFUybfyKk=; b=secU7wMBhVDUurrEX0VCmNQwcuio3aKZobrRvQnKmFZbjqzdFzEs7VNZuTBaMqkWVG +AQX/TRCJey0v6JXplHmo+SrNmQMkaxBiXzj/+Rd//CM06JzIPk2wAbpI75fdvdEVLIj pRANuk/1UYQjqR8DVrk/HW409Y5IT2H3i2wU+uHUauSU7FTxwFz8GYCwuADn3NTvo+Ox U7HVNSFHfgGcbZ++hyYRPNke+omC7qFbL/bBRt1KTtyckLCxw5PgGgRSfc0KH2O0i4BJ oaBXuVtwkMv7/4OuRrBO62j4/ZWFrwVO0DV4kQESoZdELSu8+VMuLiM6wnVatNmk1nWT grtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=sender:x-gm-message-state:from:to:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=QQa8nCgA0gmxaAgGGbAMQPhN4+fGvJKPbGeFUybfyKk=; b=WFgkB6NY18KXbrP5CgR3Q4LbupEX9SPUx8owNxZBr+haf3xiF9+M6zZRaQlo9ZMsjV UzzMkhYsay6Gy2e696eDSo7YjmazSaHvwIeD/2Ues1BSQ6SDGRBwap44PqpLeITO7hlk Fx2KhXRv/YzLOvh5emAl4A3vU5RfGd58vX1OqO5IXshI+w2TdVfEoHvjp9E6YIwMpz6k zFIKGUziDRQGrVqSwtAyKAbxsU9DEnJTZ2KSxwBhoPNVru9iOWtP+RnNon8mqqGTmYDU TEzZttO5pp9Hor/QHQ4fxOdSXac8ka/ Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AJIora9c+/36Z8uCbbWE9xzxxsZRI0D63NBEWAsd4LfpSF+XP0chiBth SGXWK/ZfPsDnC0EXpVbKIrA= X-Google-Smtp-Source: AGRyM1tbFBXwp2DcnGSUJvFb8hJaAgZsEW7dI2dfNEaSdQwoRpTWZo1xqs6evnyWe3TD2smrbd7VVQ== X-Received: by 2002:a5d:5887:0:b0:21b:ca70:f60d with SMTP id n7-20020a5d5887000000b0021bca70f60dmr15448465wrf.32.1656692222347; Fri, 01 Jul 2022 09:17:02 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a05:600c:4ec7:b0:39c:871d:313f with SMTP id g7-20020a05600c4ec700b0039c871d313fls3637826wmq.2.canary-gmail; Fri, 01 Jul 2022 09:16:58 -0700 (PDT) X-Received: by 2002:a05:600c:1e14:b0:3a0:2bba:4b2e with SMTP id ay20-20020a05600c1e1400b003a02bba4b2emr17114159wmb.196.1656692218540; Fri, 01 Jul 2022 09:16:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656692218; cv=none; d=google.com; s=arc-20160816; b=DC8ecbkA8phpPAbMG5l9+8qpRH5FqXpWVfdKQkalIGLfB3YSS/MPtiuXwKUo39Pd3K 7I/8slUtz8neBE2AgyQyiNzx5B901Qh4fcZ/KDJSNvwQaqKag9Xy95GEmcaSjPT01Pxb 1ogRbH+oA3R9Pj1h6ChVgOH9/IAHL5AUIKqd9cR9cn6b3TWTZcMNbkKctzkITx5ESFJr SG/V2IE/j1HCDA3r5syRSQdd7mf9KcgDg0yVl+3b3tFygBVadcBzHy6fwaCSM8PvE4pD 6ohkAaAwvmlKJhoKZ3Ky4Fxt4kkt+LW6E5CkuNOt1r/lnicTgDOFIVeX9KjdiALe22OV DbGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:to :from; bh=gQXy9UMMqf2cAhs+KVP4Sm8VJIEkcOQlo1cuKFOEqEY=; b=Y79/r8vYq2X/kRDfmiw9DXa0mzrsmiDAGZ+G59hFwH5YblDPF00iNxKpB561Kc3Uif mjS8NIe4vRV5mK84YnDg/2DbIGtPNxeTQ/qLbyBIaPtCvZd4UTFrXn8gzqLLzyPJDlg5 ZX1GZ6p4MouIj1a06jLcM5hzxcFPLTtZTtbJVF++sWWmSbXSFONTG5kNfJmpHOol5FXJ 5oDED9VyvtbNCVVmljTzk8KnF389XXBkLgUi1mkNnhuUjNk3SLZJPlhkLmi+amxP+Ad/ CH3HtAyDpHxnwvmAfzJmkFKPWC5za4WbK4fLMb5yNiT84DDX1T7mFtcS21KSx4Ulz0Io EpfQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of denis.maier-NSENcxR/0n0@public.gmane.org designates 130.92.0.83 as permitted sender) smtp.mailfrom=denis.maier-NSENcxR/0n0@public.gmane.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=unibe.ch Original-Received: from mailhub-lb2.unibe.ch (mailhub-lb2.unibe.ch. [130.92.0.83]) by gmr-mx.google.com with ESMTPS id f17-20020a5d58f1000000b002102a7531cesi719247wrd.2.2022.07.01.09.16.58 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 01 Jul 2022 09:16:58 -0700 (PDT) Received-SPF: pass (google.com: domain of denis.maier-NSENcxR/0n0@public.gmane.org designates 130.92.0.83 as permitted sender) client-ip=130.92.0.83; X-Virus-Scanned: By University of Bern - MGW Original-Received: from mail.campus.unibe.ch (aai-edge-01.campus.unibe.ch [130.92.13.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhub-lb2.unibe.ch (Postfix) with ESMTPS id E8250500073 for ; Fri, 1 Jul 2022 18:16:56 +0200 (CEST) Original-Received: from aai-mail-02.campus.unibe.ch (130.92.13.168) by AAI-EDGE-01.campus.unibe.ch (130.92.13.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.2507.9; Fri, 1 Jul 2022 18:16:56 +0200 Original-Received: from aai-mail-03.campus.unibe.ch (130.92.13.41) by aai-mail-02.campus.unibe.ch (130.92.13.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.2507.9; Fri, 1 Jul 2022 18:16:56 +0200 Original-Received: from aai-mail-03.campus.unibe.ch ([172.18.73.17]) by aai-mail-03.campus.unibe.ch ([172.18.73.17]) with mapi id 15.01.2507.009; Fri, 1 Jul 2022 18:16:56 +0200 Thread-Topic: Changing colons to full-stops in titles Thread-Index: AQHYjVhIsMIE8s9IhE2lBYWP9lHO8a1pnTTw///rpoCAACWJYA== In-Reply-To: Accept-Language: de-CH, en-US Content-Language: de-DE x-originating-ip: [172.18.72.2] X-Original-Sender: denis.maier-NSENcxR/0n0@public.gmane.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of denis.maier-NSENcxR/0n0@public.gmane.org designates 130.92.0.83 as permitted sender) smtp.mailfrom=denis.maier-NSENcxR/0n0@public.gmane.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=unibe.ch 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:30898 Archived-At: --_000_bc85a4891eec431f846ee69f9fcbe167unibech_ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here=E2=80=99s a very simple and absolutely unreliable version of a filter.= This will replace every colon in a title with a period. ```lua local stringify =3D pandoc.utils.stringify function Meta(m) if m.references ~=3D nil then for _, el in ipairs (m.references) do print(stringify(el.title)) el.title =3D pandoc.Str(string.gsub(stringify(el.title), ':', '.')) print(el.title) end end return m end ``` Question is how this can be made robust enough to avoid false positives. Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Im A= uftrag von John Carter Wood Gesendet: Freitag, 1. Juli 2022 17:52 An: pandoc-discuss Betreff: Re: Changing colons to full-stops in titles Thanks for the suggestions, a couple of which are kind of stretching my kno= wledge of these things, but I see where they're going. As to JGM's question: I am using a CSL json bibliography, so my titles are = in a single field. ("title":"Science and religion: new perspectives on the = dialogue") The issue is that *most* of the journals / publishers I publish in use, as = here, the colon. *Some* (mainly German) styles want the period. If I were s= olely interested in either one, I could choose and just enter the relevant = punctuation in the title field. However, I want to continue saving my bibli= ographic entries with a colon (because that's the most standard one for me)= , but have the option of automatically converting them to a period for thos= e cases where I need to. If that makes sense. Thus: going through denis's options: 1. I have switched to json bibliographies from bibtex/biblatex as they seem= ed to offer more flexibility (I was running into issue with the strange arc= hival references I have to make in my field, and JSON seemed to work better= in that regard). So this seems to not apply. 2. Seems to not apply, as I have a single title field 3. Sounds really interesting, and I use BBT, though it also sounds like I w= ould here have to create a separate bibliography file from my Zotero databa= se for those publishers/styles that require the dot. This is not *too* oner= ous, as it would at least be automated. 4. Having a filter that I could simply apply (as part of a pandoc command, = say) or not apply as relevant seems like the most flexible / efficient solu= tion. I don't know lua, but if this is one possible way, then I could use i= t as a (hopefully fairly simple?) way into learning it. Does this help to clarify my situation? denis...-NSENcxR/0n0@public.gmane.org schrieb am Freitag, 1. Juli 202= 2 um 17:34:55 UTC+2: Yes, that=E2=80=99s a known issue... There are a couple of possible solutions : 1. use biblatex databases and patch pandoc so it will concat title and subt= itle fields using periods. (line 667 https://github.com/jgm/pandoc/blob/mas= ter/src/Text/Pandoc/Citeproc/BibTeX.hs) 2. I think pandoc=E2=80=99s citeproc will just treat every unknown variable= as a string variable (see https://github.com/jgm/citeproc/blob/3f94424db46= 9c804cf2dac2d22dc7a18b614f43e/src/Citeproc/Types.hs#L1054 and https://githu= b.com/jgm/citeproc/blob/3f94424db469c804cf2dac2d22dc7a18b614f43e/src/Citepr= oc/Types.hs#L901), so you should be able to use =C2=ABsubtitle=C2=BB in sty= les. (This will give you warnings when using the style with Zotero and it w= on=E2=80=99t work reliably across implementations, but anyway ...) 3. if you=E2=80=99re using Zotero, you can leverage Zotero BBT=E2=80=99s po= stscript feature to manipulate the JSON after exporting. E.g., this one : if (Translator.BetterCSL && item.title) { reference.title =3D reference.title.replace(/ : /g, '. ') } Not bullet-proof, but simple. You will want to choose a better separator, m= aybe a double-bar or so. 4. Doing the with lua should also be possible... The question is: do you have the subtitle in a distinct field or is it just= in the title field? Von: pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Im Auftrag v= on John Carter Wood Gesendet: Freitag, 1. Juli 2022 16:39 An: pandoc-discuss Betreff: Changing colons to full-stops in titles I have one final (for now...) issue in setting up a CSL file (which I use w= ith pandoc/citeproc and references in a json file). I'm not sure whether this is a CSL issue or whether it's an issue that can = be solved via using a filter (or some other solution) in pandoc, but I thou= ght there might be some people here who might have faced a similar issue. The house style for here (German-based publisher) wants a full-stop/period = between main title and subtitle in citations / bibliographies; US/UK standa= rd is a colon between main title and subtitle. And reference managers like = Zotero -- IIUC -- save titles as single fields (at least they are in my ver= sion of Zotero). So it doesn't seem like it is possible to control what del= imiter is used between them via CSL. I have found various discussions of relevant title/subtitle division issues= -- some going back quite a few years -- in forums on Zotero: https://forums.zotero.org/discussion/8077/separate-fields-for-title-and-sub= title/ ...and CSL: https://discourse.citationstyles.org/t/handling-main-sub-title-splits-citep= roc-js/1563/11 However, these were in part discussions among developers about possible cha= nges, and I'm not sure of the current status of this issue or whether there= is a way to handle it. Would it be possible to automate turning colons in titles into full-stops v= ia using a filter? If so is there such a filter already around? Can this be= done via CSL? Or is this, as of now, impossible? (Or is there a real simple solution that I have, as usual, overlooked...) -- 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 e= mail to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/= pandoc-discuss/78df697a-50f5-46d0-b0b8-29a2cbc9509an%40googlegroups.com. -- 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 e= mail to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org. To view this discussion on the web visit https://groups.google.com/d/msgid/= pandoc-discuss/a2d540a6-a435-4285-aed5-018007d155cfn%40googlegroups.com. --=20 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 e= mail 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/bc85a4891eec431f846ee69f9fcbe167%40unibe.ch. --_000_bc85a4891eec431f846ee69f9fcbe167unibech_ Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Here=E2=80=99s a very simple and absolutely unreliable version of a f= ilter. This will replace every colon in a title with a period.

 

```lua

local stringify =3D pandoc.utils.stringify

function Meta(m)

  if m.references ~=3D nil then

    for _, el in ipairs (m.references) do

      print(stringify(el.title))<= /span>

      el.title =3D pandoc.Str(string.gsub(st= ringify(el.title), ':', '.'))

      print(el.title)

 &nb= sp;  end

  en= d

  re= turn m

end<= /o:p>

```

 

Question is how this can be made robust enough to avoid false positiv= es.

 

 

Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von John Carter Wood
Gesendet: Freitag, 1. Juli 2022 17:52
An: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Betreff: Re: Changing colons to full-stops in titles

 

Thanks for the sugges= tions, a couple of which are kind of stretching my knowledge of these thing= s, but I see where they're going.

As to JGM's question: I am using a CSL json bibliography, so my titles are = in a single field. ("title":"Science and religion: new persp= ectives on the dialogue")

The issue is that *most* of the journals / publishers I publish in use, as = here, the colon. *Some* (mainly German) styles want the period. If I were s= olely interested in either one, I could choose and just enter the relevant = punctuation in the title field. However, I want to continue saving my bibliographic entries with a colon (= because that's the most standard one for me), but have the option of automa= tically converting them to a period for those cases where I need to. If tha= t makes sense.

Thus: going through denis's options:

1. I have switched to json bibliographies from bibte= x/biblatex as they seemed to offer more flexibility (I was running into iss= ue with the strange archival references I have to make in my field, and JSO= N seemed to work better in that regard). So this seems to not apply.

2. Seems to not apply, as I have a single title fiel= d

3. Sounds really interesting, and I use BBT, though = it also sounds like I would here have to create a separate bibliography fil= e from my Zotero database for those publishers/styles that require the dot.= This is not *too* onerous, as it would at least be automated.

4. Having a filter that I could simply apply (as par= t of a pandoc command, say) or not apply as relevant seems like the most fl= exible / efficient solution. I don't know lua, but if this is one possible = way, then I could use it as a (hopefully fairly simple?) way into learning it.

 

Does this help to cla= rify my situation?

 

denis...@unibe.= ch schrieb am Freitag, 1. Juli 2022 um 17:34:55 UTC+2:

Yes, that=E2=80=99s a known issue...

There are a couple of possible solutions = ;:

 

1. use biblatex databases and patch pandoc so= it will concat title and subtitle fields using periods. (line 667 https://github.com/jgm/pandoc/blob/master/src/Text/Pandoc/C= iteproc/BibTeX.hs)

 

2. I think pandoc=E2=80=99s citeproc will just treat every unknown= variable as a string variable (see https://github.com/jgm/citeproc/blob/3f94424db4= 69c804cf2dac2d22dc7a18b614f43e/src/Citeproc/Types.hs#L1054 and https://github.com/jgm/citeproc/blob/3f94424db469c804cf2dac2d22dc7a18b614f4= 3e/src/Citeproc/Types.hs#L901), so you should be able to use =C2=ABsubt= itle=C2=BB in styles. (This will give you warnings when using the style wit= h Zotero and it won=E2=80=99t work reliably across implementations, but anyway ...)

 

3. if you=E2=80=99re using Zotero, you can le= verage Zotero BBT=E2=80=99s postscript feature to manipulate the JSON after= exporting.

E.g., this one :

if (Translator.BetterCSL && item.titl= e) {

  reference.title =3D reference.title.re= place(/ : /g, '. ')

}

Not bullet-proof, but simple. You will want t= o choose a better separator, maybe a double-bar or so.

 

4. Doing the with lua should also be possible...

 

The question is: do you have the subtitle in a distinct field or i= s it just in the title field?

 

Von: pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von John Carter Wood
Gesendet: Freitag, 1. Juli 2022 16:39
An: pandoc-discuss <pandoc-...@googl= egroups.com>
Betreff: Changing colons to full-stops in titles

 

I have one final (for now...) issue in setting up a CSL file (whic= h I use with pandoc/citeproc and references in a json file).

 

I'm not sure whether this is a CSL issue or whether it's an issue = that can be solved via using a filter (or some other solution) in pandoc, b= ut I thought there might be some people here who might have faced a similar issue.

 

The house style for here (German-based publisher) wants a full-stop/period between main title and subtitle in citations / bibl= iographies; US/UK standard is a colon between main title and subtitle. And reference managers like Z= otero -- IIUC -- save titles as single fields (at least they are in my vers= ion of Zotero). So it doesn't seem like it is possible to control what deli= miter is used between them via CSL.


I have found various discussions of relevant title/subtitle division issues= -- some going back quite a few years -- in forums on Zotero:

https://forums.zotero.org/discussion/8= 077/separate-fields-for-title-and-subtitle/

...and CSL:

https://discourse.citationstyl= es.org/t/handling-main-sub-title-splits-citeproc-js/1563/11<= /p>

 

However, these were in part discussions among developers about possible changes, and I'm not sure of the current status of this iss= ue or whether there is a way to handle it.

Would it be possible to automate turning colons in titles into ful= l-stops via using a filter? If so is there such a filter already around? Ca= n this be done via CSL?

 

Or is this, as of now, impossible?

(Or is there a real simple solution that I have, as usual, overlooked...) <= o:p>

--

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 e= mail to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/78df697a-50f5-46d0-b0b8-29= a2cbc9509an%40googlegroups.com.

--
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 pandoc-d= iscuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a2d540a6-a435-4285-aed5-01= 8007d155cfn%40googlegroups.com.

--
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/bc85a4891eec431f846ee69f9fcbe167%40unibe.ch.
--_000_bc85a4891eec431f846ee69f9fcbe167unibech_--