From: Sukil Etxenike arizaleta <sukiletxe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Why aren't review-author and review-title CSL variables supported?
Date: Wed, 2 Feb 2022 08:23:20 +0100 [thread overview]
Message-ID: <cb233f90-fc0a-0fb0-b148-ddaf74aa5090@gmail.com> (raw)
In-Reply-To: <ad5e5dda-6a05-24d9-4136-9520565f08f1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
I forgot to specify this yesterday, they are standard CSL variables. I
understand that breaking other standards to accomodate this one (no
matter others doing it) may be undesirable.
El 02/02/2022 a las 0:02, Sukil Etxenike arizaleta escribió:
> I've searched in Overleaf for Biblatex and in Bibtex.com for Bibtex
> and I've concluded that if I've searched in the right place for
> Biblatex they aren't standard fields for neither of them.
>
> Thanks,
>
> Sukil
>
>
> El 01/02/2022 a las 23:38, John MacFarlane escribió:
>> Are review-author and review-title legal bibtex or biblatex
>> fields? If so, please link to some documentation.
>>
>> Sukil Etxenike <sukiletxe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> Hello,
>>> I am currently compiling bibliography for an End of Degree Disertation.
>>> Some of this material (which I don't know if I'll finally use)
>>> consists of
>>> book reviews, published in journals, that have the review-author
>>> field (if
>>> exported to Bibtex).
>>> I've noticed Pandoc doesn't currently support this field (converting
>>> the
>>> bibtex file from bibtex to bibtex removes it), and was curious about
>>> the
>>> reason of this.
>>> (I believe I can always put the review information of the
>>> bibliography in
>>> the title field, at least in APA, and it will render fine, so this not
>>> being included doesn't worry much.)
>>> Thanks,
>>> Sukil
>>>
>>> --
>>> 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/81faa682-02f9-4bdb-8dc7-d5a016728880n%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/cb233f90-fc0a-0fb0-b148-ddaf74aa5090%40gmail.com.
next prev parent reply other threads:[~2022-02-02 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 21:59 Sukil Etxenike
[not found] ` <81faa682-02f9-4bdb-8dc7-d5a016728880n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-02-01 22:38 ` John MacFarlane
[not found] ` <yh480kczk61aca.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-02-01 23:02 ` Sukil Etxenike arizaleta
[not found] ` <ad5e5dda-6a05-24d9-4136-9520565f08f1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-02-02 7:23 ` Sukil Etxenike arizaleta [this message]
[not found] ` <cb233f90-fc0a-0fb0-b148-ddaf74aa5090-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-02-02 9:35 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <0362a4d043ab4712b3bdf16d18755c05-NSENcxR/0n0@public.gmane.org>
2022-02-02 10:15 ` Sukil Etxenike arizaleta
2022-02-02 10:15 ` Sukil Etxenike arizaleta
[not found] ` <f5bc61c0-8876-f117-c0e1-c51d716ec7a9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-02-02 10:17 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <f515be892e884f2fbce7684ad0bda537-NSENcxR/0n0@public.gmane.org>
2022-02-02 11:00 ` Sukil Etxenike arizaleta
[not found] ` <cf17bb02-d2b6-2c50-87c1-0672b3c96bd4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-02-02 14:10 ` AW: " denis.maier-NSENcxR/0n0
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=cb233f90-fc0a-0fb0-b148-ddaf74aa5090@gmail.com \
--to=sukiletxe-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).