From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: CSL YAML to "rich" bibtex?
Date: Thu, 8 Sep 2022 17:33:17 -0700 [thread overview]
Message-ID: <547DD665-7D79-4227-BA59-9C4A52512A52@gmail.com> (raw)
In-Reply-To: <569bd382-789f-b4dd-53a7-01974c970a39-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
We could consider it. Put up an issue.
> On Sep 8, 2022, at 11:05 AM, Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> wrote:
>
> I know `url` wasn't include in Patashnik [1], but it's been common since at least 2007/2008 [2] [3].
>
> Would there be an objection to including it in the bibtex output? (I'm not sure what other fields are now common in the wild, but a strength of bibtex is that it was easy to include fields that could be ignored.)
>
> [1]: https://ctan.math.illinois.edu/biblio/bibtex/base/btxdoc.pdf
> [2]: https://tug.org/pracjourn/2006-4/fenn/fenn.pdf
> [3]: https://mirrors.rit.edu/CTAN/biblio/bibtex/contrib/doc/btxFAQ.pdf
>
> On 22-08-23 12:17, John MacFarlane wrote:
>> Did you try `-t biblatex`?
>>> On Aug 23, 2022, at 8:19 AM, Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> wrote:
>>>
>>> I'm attempting to use the ACM extension for Quarto, and it requires a bibtex file.
>>>
>>> I have YAML that works with pandoc, but when I convert it to bibtex (below) it drops the `url` field -- since that's not old-school bibtex?
>>>
>>> Is there any way to get a "rich" bibtex file from CSL JSON/YAML?
>
> --
> 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/569bd382-789f-b4dd-53a7-01974c970a39%40reagle.org.
next prev parent reply other threads:[~2022-09-09 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 15:19 Joseph Reagle
[not found] ` <cf31856c-a2dd-cb42-963d-8df51c06c980-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-08-23 16:17 ` John MacFarlane
[not found] ` <DD56BDFC-DA30-49A4-BD39-C6D291B5A950-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-08-23 16:31 ` Joseph Reagle
2022-08-23 16:33 ` Joseph Reagle
[not found] ` <fbc15f9f-a158-b47c-6b10-0dba25a74f4b-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-08-23 20:06 ` Joost Kremers
2022-09-08 18:05 ` Joseph Reagle
[not found] ` <569bd382-789f-b4dd-53a7-01974c970a39-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-09-09 0:33 ` John MacFarlane [this message]
[not found] ` <547DD665-7D79-4227-BA59-9C4A52512A52-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-09-09 12:25 ` Joseph Reagle
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=547DD665-7D79-4227-BA59-9C4A52512A52@gmail.com \
--to=fiddlosopher-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).