From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: APA CSL: journal name starting with semicolon
Date: Mon, 13 Feb 2023 16:51:54 +0100 [thread overview]
Message-ID: <87sff9mrhj.fsf@zeitkraut.de> (raw)
The following BibLaTeX,
@article{Tange2011a,
address = {Frederiksberg, Denmark},
author = {Tange, O.},
doi = {10.5281/zenodo.16303},
journal = {{;login: The USENIX Magazine}},
month = Feb,
number = 1,
pages = {42-47},
title = {GNU Parallel - The Command-Line Power Tool},
url = {http://www.gnu.org/s/parallel},
volume = 36,
year = 2011
}
when processed with,
pandoc -f biblatex -t plain --citeproc --csl=apa-6th-edition.csl
yields
Tange, O. (2011). GNU parallel - the command-line power
tool;Login: The USENIX Magazine, 36(1), 42–47.
https://doi.org/10.5281/zenodo.16303
where the csl file is taken from
https://raw.githubusercontent.com/citation-style-language/styles/master/apa-6th-edition.csl
Note that the semicolon at the start of the journal title has replaced
the period that would otherwise terminate the title of the article.
Similar things happen with other styles as well, e.g., nature, but not
in pandoc's default style (chicago-author-date).
Is there some way to prevent this, either by changing the bib source or
by updating the citation style?
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
--
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/87sff9mrhj.fsf%40zeitkraut.de.
next reply other threads:[~2023-02-13 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 15:51 Albert Krewinkel [this message]
[not found] ` <87sff9mrhj.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-02-13 17:22 ` John MacFarlane
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=87sff9mrhj.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).