From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/30914 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: BPJ Newsgroups: gmane.text.pandoc Subject: Re: Changing colons to full-stops in titles Date: Mon, 4 Jul 2022 11:09:54 +0200 Message-ID: References: <78df697a-50f5-46d0-b0b8-29a2cbc9509an@googlegroups.com> <2a8d940b3675472fb4b50ead406f6fc7@unibe.ch> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001522a005e2f71a32" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23824"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCWMVYEK54FRB364RKLAMGQEICRFDPY-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mon Jul 04 11:10:12 2022 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-lf1-f62.google.com ([209.85.167.62]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o8I5s-000648-MC for gtp-pandoc-discuss@m.gmane-mx.org; Mon, 04 Jul 2022 11:10:12 +0200 Original-Received: by mail-lf1-f62.google.com with SMTP id e10-20020a19674a000000b0047f8d95f43csf2861998lfj.0 for ; Mon, 04 Jul 2022 02:10:12 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1656925811; cv=pass; d=google.com; s=arc-20160816; b=NmLrjHMf000fAnx3D/+9ZXPv26ok9uxEnnA2OX9CEd4+9KnNkV7XR6ZhmjuUKh0oET KOoKOWfJ6GATX3UNraOcxSMwXyqxESJIK1uEFpJKm97DywRUI7jKHaEYuk/+YeonWepu wbfR4rMjk343XYOdgtzZ3uMhbpuGV6RqoTaaJ1uhldkFW7x5T1j8DTh4Iwpdf08quZ1B emZKZrVapIgkanfMKfxfKtwNX4XcFdYMEjIj0zM5bJTLQCLTO6aYf1fytRk4sWYPPsqK 0Gw0vGr6WyaQ2cNxaaRkMSfone25irdnIUkffZ8/uIPP0iTDPYZWCJhek3ny3bg60QXE T0xw== 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:to:subject:message-id:date :from:in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=othcKdPrCL8k6DKPovKHIjFzKBf75la1Z3eip2uotxg=; b=fT5IO7col1GebQIf5WPcG308lJPXIydQHqL01fTM7dpNdalf5iPrhqLiw29jgwOOi8 cK1LLyzWIALMDU8mr4a67FRjyeTvvYg+K6gNneRZkVOTK3KbrsKiZzRJ2QEuo5mQhdNb quHxINkMiaoqpD1MuLXvFvYHbLPVDG1dnED6XKoyHn2N4b5LMG320r9gD6enwWgAphas GVwNzmeaESBVeTNDcKRdnPH2gSWCy5YyVtab+yv/RRzRGq4J+CnbBsa8Ob4OdUgSMKzE xDHvNjz+fHI2sQ0rjNNIw1bfVhIHg8R8llGbo/Ws0p3K6WpcwMJ/FfecD0ua6Rtwoq1e M5pA== ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=HZWvxkzX; spf=pass (google.com: domain of melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org designates 2a00:1450:4864:20::630 as permitted sender) smtp.mailfrom=melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=sender:mime-version:references:in-reply-to:from:date:message-id :subject:to: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=othcKdPrCL8k6DKPovKHIjFzKBf75la1Z3eip2uotxg=; b=G8lw/jSM7mmz0we5xxvvvTzSsO0vWOEpShDd4NhdngIsWhVMgw+i0WNCfnHEN/fOeN g0Y7qexUR7pZjGiSvB5mj6BDHLJfoCrD85UINxqbe73lXWdRyaVYzmfsbC48ZJTgMi49 bv4i4aNMYNHnjiVRsX8P8XbdkzBk2MU7AZHQM0iE0SHy/g5535QkFJElDkfE4h2BQnqZ qd608177Je/SOQ3ADELjn0pUHXbZ4kOEUMzz6UzPW2eI+L6TMclZmYAwvV5ZnZ4/re+0 VfhGLfriEOsA/6NFyusMJTQZ7iHmLDwB94Pz9exDpIWcddsWZSmgRhPv5rzBFlfLgRHl 0fDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :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=othcKdPrCL8k6DKPovKHIjFzKBf75la1Z3eip2uotxg=; b=lVqEIXDs3fAht07QumyPVcxEtqh+Fafq9dmQwEKu5phbE0Ccnh8BL7bRwyY9k41f6n GVsW/BwrJU3evyvsi08dCrGjuSz4DkbZs6/FH64g0N3yBArGtMdOz8745Qy19WOzW6st whFHTDBfQ6b7KDgr9b6eBA0cHG3Kny88uUEHfVcKJzvlBWd4ZrJ8uk8Sr1SthlpbnAFL e5GcQr3NkXIgYobSuLEa3vrsWcSaGM+VbyuHbAaNTM41cUDxotGBn2LqO1AKym6eVh01 3HgAAPYQ6pnR6QhewJFx9jW+gieBL0aPPrf9M05U6QyZSgXhFiwy2dKkI3rghnYA6z8T 1z8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=sender:x-gm-message-state:mime-version:references:in-reply-to:from :date:message-id:subject:to: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=othcKdPrCL8k6DKPovKHIjFzKBf75la1Z3eip2uotxg=; b=sAZbvw6S92u/VVdQk/wgOu9rcaclC1i8Bomlnyb4/49c2LeX1y2WKrR+QOPqZdOmBg /dbbcMFlbzlnSXp8U9UBfRk8n0eklrAJ4v4/2XSvQi9vZ28VIkVtuI17Fplpfamp/M7u 9pNFXXAsdnXy55TGMXUFt2Xeayswmtuabj5qgBCLTaeA5kP2WYlpWjAwgxkyknoCUbCw jkaFHFz9HfEtGQYuPsec1JniGWfwTVtKM1gMQG5dGZk3vni0vABLsS/joeJ98I5Z4zJM LSzkSAqPtHGLmXY1WEVi/C9pEJsMQkakTQKa8PcNe5hxEPCPup4+UsovfcTPK9/BUNkM 25dw== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AJIora910aoT8JLFd6ABy2luztysaGbx/qLj8o6Z4TRt5+Kyc4aeGENt jdUSqHVWXKYGPONiRQwbSR0= X-Google-Smtp-Source: AGRyM1u95bAEkQT874PcEmtGtREfxTDJpZ/57wztbdZalkmUNHvbb/JesTf519nU0S7WEAhJo7v/eQ== X-Received: by 2002:a19:7117:0:b0:481:97f:1031 with SMTP id m23-20020a197117000000b00481097f1031mr17736824lfc.341.1656925811643; Mon, 04 Jul 2022 02:10:11 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a05:6512:1693:b0:448:3742:2320 with SMTP id bu19-20020a056512169300b0044837422320ls56487lfb.1.gmail; Mon, 04 Jul 2022 02:10:07 -0700 (PDT) X-Received: by 2002:a05:6512:33cd:b0:47f:ad57:70d7 with SMTP id d13-20020a05651233cd00b0047fad5770d7mr19368347lfg.558.1656925806908; Mon, 04 Jul 2022 02:10:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656925806; cv=none; d=google.com; s=arc-20160816; b=hhAGZDaO2H9zhsh4Mrv/WdysEr3pBMmHqv71Se047JkkD3WNUXaBATipxNISA6NT40 bxlkuTZ5mCvt4OSKV2xhD8gIGwWE0Np/Ce+W+1uwqCH/MbZ5FBTly/nCFUMeyG7ARA+q 9vFeITOTXHmH5sO2rWNtbP0Q6A/eCu8Q310/P94YUszoobDj8m/Ne6jV1nU8uHGy7IyQ Ruw+2wpjiW4HnXW7DTBuxd3VpKFzZj2qeigCdb8Gg3bzkl3DSWID3g4xO8d14EcSJXOH bh/3HXnvH+2Mwe+VQdKiQvne+9akNfs0Z8bMpzRduG2XUSMnAnXgNsS1lm9VBVTOXOAs FkhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=KnurIX61msUZ0V764iVnDilc89C9LuUqCWaCW1yLWsw=; b=NBVLRsDt8hXozSzDe2W05e+scUEQA4X3e8rUJE0h3/gGsBDFnAG3gdcldkJOgi7Qup awaToi6uqcNFmnbqNgey/SyiYCQidmRFmCGOp3WJuXCcHAws+qWhrejiIHQkR+jn8heP X0xdwtGYsjvUQS4tosbkqZ2YD8SOD2o8E+jDEBGoH2QIOljxj8GUpBpshxLycFwQn/Z4 7ZjzENssBO+d5UxXxrYWxQHEWGGE5HZh9H1NJkblqh7wbdgbWz3+V1/J1QHPGpYgwHM4 Ck5LVRXyniyOtPn9XKfYE1/qiFbLp7qyHk1KNpIjT85pzbURBjLLkd6eQ7ybLUVQVphC 3tzA== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=HZWvxkzX; spf=pass (google.com: domain of melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org designates 2a00:1450:4864:20::630 as permitted sender) smtp.mailfrom=melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Original-Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com. [2a00:1450:4864:20::630]) by gmr-mx.google.com with ESMTPS id g14-20020a0565123b8e00b004810be25317si979528lfv.4.2022.07.04.02.10.06 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Jul 2022 02:10:06 -0700 (PDT) Received-SPF: pass (google.com: domain of melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org designates 2a00:1450:4864:20::630 as permitted sender) client-ip=2a00:1450:4864:20::630; Original-Received: by mail-ej1-x630.google.com with SMTP id lw20so15603801ejb.4 for ; Mon, 04 Jul 2022 02:10:06 -0700 (PDT) X-Received: by 2002:a17:906:830c:b0:726:a68b:d1bc with SMTP id j12-20020a170906830c00b00726a68bd1bcmr27792828ejx.305.1656925805944; Mon, 04 Jul 2022 02:10:05 -0700 (PDT) In-Reply-To: X-Original-Sender: melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=HZWvxkzX; spf=pass (google.com: domain of melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org designates 2a00:1450:4864:20::630 as permitted sender) smtp.mailfrom=melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com 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:30914 Archived-At: --0000000000001522a005e2f71a32 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It turns out "my" bug is already fixed in the development version of LaTeX::ToUnicode. Compare the CPAN version https://metacpan.org/dist/LaTeX-ToUnicode/source/lib/LaTeX/ToUnicode.pm#L46 with current master: https://github.com/borisveytsman/BibTeXPerlLibs/blob/5d24b66bd2461f1f3fc4d9= a28dd8774ad6c75829/LaTeX-ToUnicode/lib/LaTeX/ToUnicode.pm#L314 The crucial difference is `\w{1,1}` vs. `\w{1,2}`. Given e.g. `Fr\"oding` the latter would always match two letters and try to look up `$ACCENTS{'"'}{od}` rather than `$ACCENTS{'"'}{o}`, which would fail. You should be able to install the development version by cloning the GitHub repo, coding to LaTeX-ToUnicode and saying `cpanm --force .` The force is because a couple of conversion tests (`\$` -> `$` and `\&` -> `&`) still fail. If you don't have cpanm installed you need to say `cpan App::cpanminus` first. However it still fails one of my test cases which I wrote yesterday: it leaves inputs like `\'{\ae}` and `\"{\ae}` which TeX is perfectly fine with as `\'=C3=A6 \"=C3=A6`. The first of these exists precomposed in Unicode be= cause Danish sometimes uses it so is definitely a bug and the second should arguably be replaced with letter + combining mark, so I will likely make a couple of pull requests as and when I have time. /bpj Den s=C3=B6n 3 juli 2022 21:43BPJ skrev: > > > Den s=C3=B6n 3 juli 2022 18:55Paulo Ney de Souza skr= ev: > >> >> On Sun, Jul 3, 2022 at 5:15 AM BPJ wrote: >> >>> It's an upstream bug in LaTeX::ToUnicode. >>> >> >> On LaTeX::ToUnicode ? I thought you only used BibTeX::Parser. >> > > Which uses LaTeX::ToUnicode in its `cleaned_*` methods. > > > >> I just had never run into it AFAIK because all the .bib files I had >>> written myself or downloaded from the libraries I use had used `\"{a}` >>> rather than `\"a` which doesn't hit the bug. I have located the bug and= am >>> working on a patch. Thanks for discovering this! (There are a lot of >>> unattended bugs though. Do you want me to send you the patch when it is >>> ready?) >>> >> >> I know of some bugs on BibTeX::Parser (and none on LaTeX::ToUnicode). >> > > There are some on the old CPAN RT tracker. I don't know if they are de > facto fixed. > > > It would be nice to have all of them listed o the issues of the project >> page: >> >> https://github.com/borisveytsman/BibTeXPerlLibs/issues >> > > Thanks for the link. It is missing on MetaCPAN. One of the old bugs > complains about sloppy packaging. > > > >> especially if you are producing a patch. >> > > Well it will be listed when I submit a PR! > > > >> Paulo Ney >> >> >> >>> Den s=C3=B6n 3 juli 2022 07:42Paulo Ney de Souza s= krev: >>> >>>> I got interested in another aspect of the posting -- the program " >>>> cleanbib.pl" by Benct. >>>> >>>> I installed it in Ubuntu, and found out it does not process perfectly >>>> valid TeX code like characters that end or have a space in the middle,= or >>>> that it processes \c{e}, but not the comma-accent any of the other vow= els... >>>> >>>> I prepared the torture test below to show the problems: >>>> >>>> @Book{hobbit, >>>> title =3D {Les \oe uf de la serpente}, >>>> address =3D {Bla\v zi\'c}, >>>> publisher =3D {\c{a} \c{e} \c{i} \c{o} \c{u}}, >>>> } >>>> >>>> and above all, how does this compare to: >>>> >>>> https://ctan.org/tex-archive/support/bibtexperllibs/LaTeX-ToUnicod= e >>>> >>>> Paulo Ney >>>> >>>> >>>> On Sat, Jul 2, 2022 at 1:03 PM BPJ wrote: >>>> >>>>> string.gsub() optionally takes the maximum number of substitutions as >>>>> a fourth argument, and you can reinsert capture groups in the replace= ment, >>>>> so this should be fairly robust: >>>>> >>>>> ``````lua >>>>> string.gsub(title, '%:(%s)', '.%1', 1) >>>>> `````` >>>>> >>>>> >>>>> Den fre 1 juli 2022 18:44John Carter Wood skrev= : >>>>> >>>>>> Ah, of course, biblical references. Religious history is one of my >>>>>> fields, how could I miss that? >>>>>> >>>>>> Looking forward to trying this out! >>>>>> >>>>>> denis...-NSENcxR/0n0@public.gmane.org schrieb am Freitag, 1. Juli 2022 um 18:41:02 UTC+2= : >>>>>> >>>>>>> A slightly more reliable version: >>>>>>> >>>>>>> >>>>>>> >>>>>>> ``` >>>>>>> >>>>>>> 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``` >>>>>>> >>>>>>> >>>>>>> >>>>>>> (This won=E2=80=99t replace colons in biblical references, e.g. Gen= 1:1) >>>>>>> >>>>>>> >>>>>>> >>>>>>> You can test with this file : >>>>>>> >>>>>>> >>>>>>> >>>>>>> ```markdown >>>>>>> >>>>>>> --- >>>>>>> >>>>>>> references: >>>>>>> >>>>>>> - type: book >>>>>>> >>>>>>> id: doe >>>>>>> >>>>>>> author: >>>>>>> >>>>>>> - family: Doe >>>>>>> >>>>>>> given: Jane >>>>>>> >>>>>>> issued: >>>>>>> >>>>>>> date-parts: >>>>>>> >>>>>>> - - 2022 >>>>>>> >>>>>>> title: 'A book: with a subtitle and a reference to Gen 1:1, but >>>>>>> that is not a problem' >>>>>>> >>>>>>> publisher: 'Whatever press' >>>>>>> >>>>>>> lang: de-De >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> >>>>>>> >>>>>>> test [@doe] >>>>>>> >>>>>>> ``` >>>>>>> >>>>>>> >>>>>>> >>>>>>> The filter itself does not cover capitalization. For some reason, >>>>>>> pandoc or citeproc applies title-case transformation here. I don=E2= =80=99t think it >>>>>>> should though. >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Von:* pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org *I= m >>>>>>> Auftrag von *John Carter Wood >>>>>>> *Gesendet:* Freitag, 1. Juli 2022 18:24 >>>>>>> *An:* pandoc-discuss >>>>>>> *Betreff:* Re: Changing colons to full-stops in titles >>>>>>> >>>>>>> >>>>>>> >>>>>>> That's very interesting, thanks! I'll try it out when I get a chanc= e >>>>>>> in the coming days. >>>>>>> >>>>>>> I have thought about this issue of false positives while thinking >>>>>>> about the option of some kind of filter. But...I think they would b= e very >>>>>>> rare. I have a hard time thinking of a title with a colon in it tha= t >>>>>>> shouldn't be -- in this case -- be turned into a dot. At least, I d= on't >>>>>>> have anything in my 1,200 references where I can see that that woul= dn't >>>>>>> apply. >>>>>>> >>>>>>> Although, of course, I'm sure there are some out there... >>>>>>> >>>>>>> Just a question: would this also ensure that the first word after >>>>>>> the dot is capitalised? Or does that open a new series of problems?= :-) >>>>>>> >>>>>>> >>>>>>> denis...-NSENcxR/0n0@public.gmane.org schrieb am Freitag, 1. Juli 2022 um 18:17:02 >>>>>>> UTC+2: >>>>>>> >>>>>>> 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org *I= m >>>>>>> Auftrag 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 stretchin= g >>>>>>> my knowledge 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 per= iod. If >>>>>>> I were solely interested in either one, I could choose and just ent= er the >>>>>>> relevant punctuation in the title field. However, I want to continu= e saving >>>>>>> my bibliographic entries with a colon (because that's the most stan= dard one >>>>>>> for me), but have the option of automatically converting them to a = period >>>>>>> for those 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 seemed to offer more flexibility (I was running into issue wit= h the >>>>>>> strange archival references I have to make in my field, and JSON se= emed 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 would here have to create a separate bibliography file from = my >>>>>>> Zotero database for those publishers/styles that require the dot. T= his is >>>>>>> not *too* onerous, 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 solution. I don't know lua, but if this is one possible w= ay, then >>>>>>> I could use it 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 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/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/3f94424db469c804cf2dac2d22dc7a= 18b614f43e/src/Citeproc/Types.hs#L1054 >>>>>>> and >>>>>>> https://github.com/jgm/citeproc/blob/3f94424db469c804cf2dac2d22dc7a= 18b614f43e/src/Citeproc/Types.hs#L901), >>>>>>> so you should be able to use =C2=ABsubtitle=C2=BB in styles. (This = will give you >>>>>>> warnings when using the style with Zotero and it won=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 postscript >>>>>>> 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, 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 is >>>>>>> it just in the title field? >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Von:* pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org *I= m >>>>>>> Auftrag von *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 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 p= andoc, >>>>>>> but 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-sto= p/period >>>>>>> *between main title and subtitle in citations / bibliographies; >>>>>>> US/UK standard is a *colon* between main title and subtitle. And >>>>>>> reference managers like Zotero -- IIUC -- save titles as single fie= lds (at >>>>>>> least they are in my version of Zotero). So it doesn't seem like it= is >>>>>>> possible to control what delimiter is used between them via CSL. >>>>>>> >>>>>>> >>>>>>> I have found various discussions of relevant title/subtitle divisio= n >>>>>>> issues -- some going back quite a few years -- in forums on Zotero: >>>>>>> >>>>>>> >>>>>>> https://forums.zotero.org/discussion/8077/separate-fields-for-title= -and-subtitle/ >>>>>>> >>>>>>> ...and CSL: >>>>>>> >>>>>>> >>>>>>> https://discourse.citationstyles.org/t/handling-main-sub-title-spli= ts-citeproc-js/1563/11 >>>>>>> >>>>>>> >>>>>>> >>>>>>> However, these were in part discussions among developers about >>>>>>> *possible* changes, 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 via 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 email 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 email 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/a2d540a6-a435-4285= -aed5-018007d155cfn%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 email 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/f0f222ef-e60e-4397= -83ac-bec1a6ac2d08n%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 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/b3deb0de-8ba0-4159-= b9f3-1ecfbe68d457n%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, sen= d >>>>> 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/CADAJKhAU66TxJKMZdDM= -KVabJpmKUVo5xyuAAN03F2b89jv9Ow%40mail.gmail.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 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/CAFVhNZMyj_GZ%3DAo_1q= R2rwnAAYAaQ%3DMaf880cGLRv7yD_ianpQ%40mail.gmail.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 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/CADAJKhBjTdgbY-xDouhDG= fnE%2BJ%2BV5c3v0FUA2Hn00z59%3D%3DWeLw%40mail.gmail.com >>> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Group= s >> "pandoc-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send a= n >> 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/CAFVhNZNNsfQs_Lt8agoase= yrNfdhrVOC9GTusMEdfecJFCBnug%40mail.gmail.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/CADAJKhB7xCir7Gwq%3DXr%3DYh4jSfCfjqnfWNdWvYZoXE7idcbePQ%40ma= il.gmail.com. --0000000000001522a005e2f71a32 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It turns out "my" bug is already fixed in the d= evelopment version of LaTeX::ToUnicode. Compare the CPAN version


with current master:

<= div dir=3D"auto">
The crucial difference is `\w{= 1,1}` vs. `\w{1,2}`. Given e.g. `Fr\"oding` the latter would always ma= tch two letters and try to look up `$ACCENTS{'"'}{od}` rather = than `$ACCENTS{'"'}{o}`, which would fail.

You should be able to install the developme= nt version by cloning the GitHub repo, coding to LaTeX-ToUnicode and saying= `cpanm --force .` The force is because a couple of conversion tests (`\$` = -> `$` and `\&` -> `&`) still fail. If you don't have cpa= nm installed you need to say `cpan App::cpanminus` first.

However it still fails one of my test cas= es which I wrote yesterday: it leaves inputs like `\'{\ae}` and `\"= ;{\ae}` which TeX is perfectly fine with as `\'=C3=A6 \"=C3=A6`. T= he first of these exists precomposed in Unicode because Danish sometimes us= es it so is definitely a bug and the second should arguably be replaced wit= h letter + combining mark, so I will likely make a couple of pull requests = as and when I have time.

/bpj


Den s=C3=B6n 3 juli 2022 21:43BPJ &l= t;melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:


Den s=C3=B6n 3 juli = 2022 18:55Paulo Ney de Souza <pauloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:

On Sun, Jul 3, 2022 at 5:15 AM BPJ <= melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org= > wrote:
It's an upstream bug in LaTeX::To= Unicode.

On=C2=A0 LaTeX::ToUnicode ? = I thought you only used BibTeX::Parser.

Which uses LaTeX::ToUn= icode in its `cleaned_*` methods.



<= /div>
I = just had never run into it AFAIK because all the .bib files I had written m= yself or downloaded from the libraries I use had used `\"{a}` rather t= han `\"a` which doesn't hit the bug. I have located the bug and am= working on a patch. Thanks for discovering this! (There are a lot of unatt= ended bugs though. Do you want me to send you the patch when it is ready?)<= /div>

I know of some bugs on BibTeX::Parser= (and none on LaTeX::ToUnicode).

There are some on the old CP= AN RT tracker. I don't know if they are de facto fixed.


It would be nice to have all of them listed o the=C2= =A0issues of the project page:


Thanks for the link. It is missing on MetaCPAN. One of the old bugs c= omplains about sloppy packaging.



<= /div>
especially if you are producing a patch.

Well it wil= l be listed when I submit a PR!



<= /div>
Paulo Ney



De= n s=C3=B6n 3 juli 2022 07:42Paulo Ney de Souza <pauloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:=
I got interested in another=C2=A0aspect of the posting -- the program &qu= ot;cl= eanbib.pl" by Benct.

I installed=C2=A0it in Ubu= ntu, and found out it does not process perfectly valid TeX code like charac= ters that end or have a space in the middle, or that it processes \c{e}, bu= t not the comma-accent any of the other vowels...

<= div>I prepared the torture test below to show the problems:

<= /div>
@Book{hobbit,
=C2=A0 title =C2=A0 =C2=A0=3D {Les \oe uf =C2=A0= de la serpente},
=C2=A0 address =3D {Bla\v zi\'c},
=C2=A0 publish= er =3D {\c{a} \c{e} \c{i} \c{o} \c{u}},
}=C2=A0

=
and above all, how does this compare to:


Paulo Ney


<= div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jul 2, 2022 at 1:03 PM BPJ <= ;b= pj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org> wrote:
string.gsub() optionally takes the maximum n= umber of substitutions as a fourth argument, and you can reinsert capture g= roups in the replacement, so this should be fairly robust:

``````lua
string.gsub(t= itle, '%:(%s)', '.%1', 1)
``````


Den fre 1 juli 2022 18:44John Carter Wood <= ;woodjo-ZOsAvrTRSvuEhhMi0yms2Q@public.gmane.org> skrev:
Ah, of course, biblical references. Religious histor= y is one of my fields, how could I miss that?

Looking forward to tr= ying this out!

denis...-NSENcxR/0n0@public.gmane.org schrieb am Freitag, 1. Juli = 2022 um 18:41:02 UTC+2:

A slightly more reliable versio= n:

=C2=A0

```

local stringify =3D pandoc.util= s.stringify

function Meta(m)<= /span>

=C2=A0 if m.references ~=3D nil= then

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

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- print(stringify(el.title))

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = el.title =3D pandoc.Str(string.gsub(stringify(el.title), ': ', '= ;. '))

=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 -- print(el.title)

=C2=A0=C2=A0=C2=A0 end

=C2=A0 end

=C2=A0 return m

end```

=C2=A0

(This won=E2=80=99t replace colons in biblical references, e.g. Gen 1= :1)

=C2=A0

You can test with this file=C2= =A0:

=C2=A0

```markdown

---

references:

- type: book

=C2=A0 id: doe

=C2=A0 author:

=C2=A0 - family: Doe

=C2=A0=C2=A0=C2=A0 given: Jane

=C2=A0 issued:<= /u>

=C2=A0=C2=A0=C2=A0 date-parts:<= u>

=C2=A0=C2=A0=C2=A0 - - 2022<= /u>

=C2=A0 title: 'A book: with= a subtitle and a reference to Gen 1:1, but that is not a problem'

=C2=A0 publisher: 'Whatever= press'

=C2=A0 lang: de-De

...

=C2=A0

test [@doe]

```

=C2=A0

The filter itself does not cover capitalizatio= n. For some reason, pandoc or citeproc applies tit= le-case transformation here. I don=E2=80=99t think it should though.=

=C2=A0

Von: pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<= /a> <pandoc-...@googlegroups= .com> Im Auftrag von John Carter Wood
Gesendet: Freitag, 1. Juli 2022 18:24
An: pandoc-discuss <p= andoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Betreff: Re: Changing colons to full-stops in titles

=C2=A0

That's very interes= ting, thanks! I'll try it out when I get a chance in the coming days.

I have thought about this issue of false positives while thinking about the= option of some kind of filter. But...I think they would be very rare. I ha= ve a hard time thinking of a title with a colon in it that shouldn't be= -- in this case -- be turned into a dot. At least, I don't have anything in my 1,200 references where I ca= n see that that wouldn't apply.

Although, of course, I'm sure there are some out there...

Just a question: would this also ensure that the first word after the dot i= s capitalised? Or does that open a new series of problems? :-)


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

Here=E2=80=99s a very simple an= d absolutely unreliable version of a filter. This will replace every colon = in a title with a period.

=C2=A0

```lua

local stringify =3D pandoc.util= s.stringify

function Meta(m)<= u>

=C2=A0 if m.references ~=3D nil= then

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

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = print(stringify(el.title))

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = el.title =3D pandoc.Str(string.gsub(stringify(el.title), ':', '= .'))

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 print(el.title)

=C2=A0=C2=A0=C2=A0 end

=C2=A0 end

=C2=A0 return m

end

```

=C2=A0

Question is how this can be mad= e robust enough to avoid false positives.

=C2=A0

=C2=A0

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

=C2=A0

Thanks for the suggesti= ons, a couple of which are kind of stretching my knowledge 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 p= erspectives 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 au= tomatically converting them to a period for those cases where I need to. If= that 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 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 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 a= utomated.

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 si= mple?) way into learning it.

=C2=A0

Does this help to clari= fy my situation?

=C2=A0

de= nis...-NSENcxR/0n0@public.gmane.org schrieb am Freitag, 1. Juli 2022 um 17:34:55 UTC= +2:

Yes, that=E2=80=99s a known iss= ue...

There are a couple of possible = solutions=C2=A0:

=C2=A0

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

=C2=A0

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/3f94424db469c804cf2dac2d22dc7a18b614f43e/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 ...)

=C2=A0

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

E.g., this one=C2=A0:=

if (Translator.BetterCSL &&= amp; item.title) {

=C2=A0 reference.title =3D refe= rence.title.replace(/ : /g, '. ')

}

Not bullet-proof, but simple. Y= ou will want to choose a better separator, maybe a double-bar or so.=

=C2=A0

4. Doing the with lua should also be possible...<= /u>

=C2=A0

The question is: do you have the subtitle in a disti= nct field or is it just in the title field?

=C2=A0

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

=C2=A0

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

=C2=A0

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

=C2=A0

The house style for here (German-based publisher) wa= nts 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 = delimiter 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-= subtitle/

...and CSL:

https://discourse.citationstyles.org/t/handling-main-sub-title-= splits-citeproc-js/1563/11

=C2=A0

However, these were in = part discussions among developers about possible changes, 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 t= itles into full-stops via using a filter? If so is there such a filter alre= ady around? Can this be done via CSL?

=C2=A0

Or is this, as of now, impossible?

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

--

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...@googlegr= oups.com.
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-discus...@googlegr= oups.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-discus...@googlegroups.c= om.

--
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-discuss+unsubscribe@g= ooglegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss= /b3deb0de-8ba0-4159-b9f3-1ecfbe68d457n%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-discuss+unsubscribe@googlegroups= .com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discus= s/CADAJKhAU66TxJKMZdDM-KVabJpmKUVo5xyuAAN03F2b89jv9Ow%40mail.gmail.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-discuss+unsubscribe@googlegroups= .com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-di= scuss/CAFVhNZMyj_GZ%3DAo_1qR2rwnAAYAaQ%3DMaf880cGLRv7yD_ianpQ%40mail.gmail.= 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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhBjTdg= bY-xDouhDGfnE%2BJ%2BV5c3v0FUA2Hn00z59%3D%3DWeLw%40mail.gmail.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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAFVhNZNNsfQs_Lt8ago= aseyrNfdhrVOC9GTusMEdfecJFCBnug%40mail.gmail.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://gro= ups.google.com/d/msgid/pandoc-discuss/CADAJKhB7xCir7Gwq%3DXr%3DYh4jSfCfjqnf= WNdWvYZoXE7idcbePQ%40mail.gmail.com.
--0000000000001522a005e2f71a32--