public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Nick Bart' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Year appears twice in biblio item from @online biblatex entry
Date: Fri, 23 Sep 2022 19:23:13 +0000	[thread overview]
Message-ID: <Awmp_-n0ldFy73juJM-rHKUPA5-zKZrZvo9DhcuCMaBSPlcEdCGvYZYNWQFYcNqOgjYD7OIrHqaWzl_lJdE7MOfRdtYzPtVy3D_6bjvaG10=@protonmail.com> (raw)
In-Reply-To: <d8d0b9e0-014f-42a5-a223-c5bfcc6dab7cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

I don't have a clear solution, but it looks like the root cause is that in the absence of an author,  the title is moved to the beginning position *and* the date consists only of the year.

Adding a full date to the example from the initial post the result is

“A DSL That Is Concise and Fun.” 2021. November 23, 2021.
https://web.archive.org/web/20211216060806/https://twitter.com/scalding.

... and adding an author as well results in

Scalding. 2021. “A DSL That Is Concise and Fun.” November 23, 2021.
https://web.archive.org/web/20211216060806/https://twitter.com/scalding.

Now, at least the latter results looks perfectly normal, so I don't think this is a CSL style issue per se.

I guess in principle, the mechanism that moves the title could be made to also check whether this leaves years or a date and a year side by side.

On the other hand, I'm not sure this is really worthwhile, since in practice you should probably always include an organization field in the biblatex data, which in turn ensures that the year and full date are separate, even if there is no author and the title is moved.

-- 
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/Awmp_-n0ldFy73juJM-rHKUPA5-zKZrZvo9DhcuCMaBSPlcEdCGvYZYNWQFYcNqOgjYD7OIrHqaWzl_lJdE7MOfRdtYzPtVy3D_6bjvaG10%3D%40protonmail.com.

[-- Attachment #2: Type: text/html, Size: 2578 bytes --]

  parent reply	other threads:[~2022-09-23 19:23 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
     [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 [this message]
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='Awmp_-n0ldFy73juJM-rHKUPA5-zKZrZvo9DhcuCMaBSPlcEdCGvYZYNWQFYcNqOgjYD7OIrHqaWzl_lJdE7MOfRdtYzPtVy3D_6bjvaG10=@protonmail.com' \
    --to=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).