public inbox archive for
 help / color / mirror / Atom feed
From: iandol <>
To: pandoc-discuss <pandoc-discuss-/>
Subject: Re: BibLaTeX data model using YAML syntax, possible?
Date: Wed, 6 Dec 2023 16:47:45 -0800 (PST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <23908cfd-bd5e-46c0-b1e6-65c8a082dd1fn-/>

[-- Attachment #1.1: Type: text/plain, Size: 1823 bytes --]

I can't respond to your specific issue, but just to throw another potential 
into the mix, the Typst team made their own YAML bibliography format and 

They have a CLI to convert to BibLaTeX, which Pandoc can read, so that may 
be one solution depending on how you feel about the Hayagriva data model...


On Wednesday 6 December 2023 at 00:41:54 UTC+8 wrote:

> 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/
To view this discussion on the web visit

[-- Attachment #1.2: Type: text/html, Size: 2467 bytes --]

      parent reply	other threads:[~2023-12-07  0:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 16:41
     [not found] ` <23908cfd-bd5e-46c0-b1e6-65c8a082dd1fn-/>
2023-12-07  0:47   ` iandol [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \
    --cc=pandoc-discuss-/ \

* 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).