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: Year appears twice in biblio item from @online biblatex entry
Date: Thu, 22 Sep 2022 12:35:14 -0700 (PDT)	[thread overview]
Message-ID: <826a8e3a-24ed-407d-bc2b-8320ac9a75e0n@googlegroups.com> (raw)


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

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-discuss+unsubscribe-/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.

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

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 19:35 Antonio Piccolboni [this message]
     [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
     [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=826a8e3a-24ed-407d-bc2b-8320ac9a75e0n@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).