From: "lucabal...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <lucabalsanelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: BibLaTeX data model using YAML syntax, possible?
Date: Tue, 5 Dec 2023 08:41:54 -0800 (PST) [thread overview]
Message-ID: <23908cfd-bd5e-46c0-b1e6-65c8a082dd1fn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1319 bytes --]
Hi,
I'd like to use a YAML file format, which I consider easier to write and
more human-readable w.r.t. bib format, but using the biblatex data model
(defined in chapter 2 of BibLaTeX manual, found at ctan/biblatex), which I
prefer over CSL data model (defined in appendix III and IV of CSL 1.0.2
specifications).
As far as I understand, by default, pandoc expects (ref. pandoc/manual,
sec. Specifying bibliographic data)
BibLaTeX data in a file formatted as .bib
BibTeX data in a file formatted as .bib (and and extension as .bibtex)
CSL data in a file formatted as JSON
CSL data in a file formatted as YAML
RIS data in a file formatted as .ris
Is it a way to use BibLaTeX data model in a YAML formatted file? Is there
any caveats? There is a need of a Lua Filter? What does pandoc use to parse
.yaml or .bib files and to write those? Where should I begin?
Thanks,
Luca
--
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/23908cfd-bd5e-46c0-b1e6-65c8a082dd1fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1723 bytes --]
next reply other threads:[~2023-12-05 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 16:41 lucabal...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
[not found] ` <23908cfd-bd5e-46c0-b1e6-65c8a082dd1fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-07 0:47 ` iandol
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=23908cfd-bd5e-46c0-b1e6-65c8a082dd1fn@googlegroups.com \
--to=lucabalsanelli-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).