public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Antonio Piccolboni <piccolbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Year appears twice in biblio item from @online biblatex entry
Date: Thu, 22 Sep 2022 15:03:21 -0700 (PDT)	[thread overview]
Message-ID: <6300be55-0355-4427-9e48-730a1656ffc9n@googlegroups.com> (raw)
In-Reply-To: <YyzJaxV2nPho4ZdX@localhost>


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

In what field am I suppose to enter that "June 8, 2021"? I tried year and 
urldate. The former is repeated twice verbatim, the latter ignored. Thanks
On Thursday, September 22, 2022 at 1:45:43 PM UTC-7 Bastien Dumont wrote:

> Or to write a Lua filter, of course!
>
> Le Thursday 22 September 2022 à 08:44:17PM, Bastien DUMONT a écrit :
> > This is because the group ending with a dot contains the author-year 
> form of the reference with the year only, whereas the second date is part 
> of the full reference and would contain the full date if it were provided. 
> The solution is to provide more information in order to get an output like 
> this one:
> > 
> > Doe, John. 2021. “A DSL That Is Concise and Fun.” Twitter. June 8, 2021. 
> https://web.archive.org/web/20211216060806/https://twitter.com/scalding.
> > 
> > Le Thursday 22 September 2022 à 12:49:11PM, John MacFarlane a écrit :
> > > the CSL has
> > > 
> > > <layout suffix=".">
> > > <group delimiter=". ">
> > > <text macro="contributors"/>
> > > <text macro="date"/>
> > > <text macro="title"/>
> > > </group>
> > > <text macro="description"/>
> > > <text macro="secondary-contributors" prefix=". "/>
> > > <text macro="container-title" prefix=". "/>
> > > <text macro="container-contributors"/>
> > > <text macro="edition"/>
> > > <text macro="locators-chapter"/>
> > > <text macro="collection-title-journal" prefix=", " suffix=", "/>
> > > <text macro="locators"/>
> > > <text macro="collection-title" prefix=". "/>
> > > <text macro="issue"/>
> > > <text macro="locators-article"/>
> > > <text macro="access" prefix=". "/>
> > > </layout>
> > > 
> > > 
> > > and I think the first date is coming from the "date" macro, while the 
> second is coming from "access," which for web_page uses "issued" date.
> > > 
> > > I don't know if this is a bug in the style or if there's some subtlety 
> that's wrong in pandoc's CSL processing. Maybe a CSL expert can chime in 
> here? Or try using Zotero with chicago-author-date.csl to see what it does.
> > > 
> > > > On Sep 22, 2022, at 12:35 PM, Antonio Piccolboni <picc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 
> wrote:
> > > > 
> > > > Hi, I am producing pdf and epub from markdown. The bibliography is 
> in biblatex. There is a problem with @online items in that the year is 
> repeated twice in the output, be it pdf or epub. This is an entry:
> > > > 
> > > > 
> > > > 
> > > > @online{scalding,
> > > > title={A DSL that is concise and fun},
> > > > url={
> https://web.archive.org/web/20211216060806/https://twitter.com/scalding},
> > > > year={2021}
> > > > }
> > > > 
> > > > And this is the result:
> > > > 
> > > > “A DSL That Is Concise and Fun.” 2021. 2021. 
> https://web.archive.org/web/20211216060806/https://twitter.com/scalding.
> > > > 
> > > > I am using the options --citeproc --bibliography biblio.biblatex
> > > > 
> > > > Other item types look just fine.
> > > > Any suggestions? Thanks
> > > > 
> > > > 
> > > > Antonio
> > > > 
> > > > -- 
> > > > 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/826a8e3a-24ed-407d-bc2b-8320ac9a75e0n%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/B3269C33-2E6B-403C-BC73-4139FC900699%40gmail.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/YyzJIbTFWQuWhF0R%40localhost
> .
>

-- 
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/6300be55-0355-4427-9e48-730a1656ffc9n%40googlegroups.com.

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

  reply	other threads:[~2022-09-22 22:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 19:35 Antonio Piccolboni
     [not found] ` <826a8e3a-24ed-407d-bc2b-8320ac9a75e0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-22 19:49   ` John MacFarlane
     [not found]     ` <B3269C33-2E6B-403C-BC73-4139FC900699-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-09-22 20:44       ` Bastien DUMONT
2022-09-22 20:45         ` Bastien DUMONT
2022-09-22 22:03           ` Antonio Piccolboni [this message]
     [not found]             ` <6300be55-0355-4427-9e48-730a1656ffc9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-23  6:16               ` Bastien DUMONT
2022-09-23  6:26               ` Bastien DUMONT
2022-09-23  6:35                 ` Antonio Piccolboni
     [not found]                   ` <568b34c1-c26d-4e14-8c7c-6c503d7a34een-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-23  8:07                     ` Bastien DUMONT
2022-09-23 16:09                       ` Antonio Piccolboni
     [not found]                         ` <d8d0b9e0-014f-42a5-a223-c5bfcc6dab7cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-23 19:23                           ` 'Nick Bart' via pandoc-discuss
2022-09-23 20:54                             ` Antonio Piccolboni
     [not found]                               ` <479b45ca-ec3a-4d0b-8dff-a2639548c6a5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-23 21:13                                 ` 'Nick Bart' via pandoc-discuss

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=6300be55-0355-4427-9e48-730a1656ffc9n@googlegroups.com \
    --to=piccolbo-re5jqeeqqe8avxtiumwx3w@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).