public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: A little confused on how pandoc converts bibliographies....
Date: Fri, 22 Jul 2022 14:33:48 +0200	[thread overview]
Message-ID: <CAMwawgPWu2H_M82nP93LuY-v+jVHbvax-Jppbd4pn9jPNANWoA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

Dear All,

It seems to me that the way pandoc handles bibliographies is slighty
different from how it handles other formats. After doing some checks, it
looks individual bibliographic elements are not converted to AST elements
but rather Metadata elements. This is true at the very least for markdown.

Could anyone point to some resources, information or perhaps source code
for how pandoc specifically handles LaTeX based bibliographies such as
BibTeX or BibLaTeX? Are the readers and writers for these formats written
in Lua? If so where can I find them?

Regards,

Amine

-- 
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/CAMwawgPWu2H_M82nP93LuY-v%2BjVHbvax-Jppbd4pn9jPNANWoA%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 1416 bytes --]

             reply	other threads:[~2022-07-22 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 12:33 A A [this message]
     [not found] ` <CAMwawgPWu2H_M82nP93LuY-v+jVHbvax-Jppbd4pn9jPNANWoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-22 16:34   ` Sukil Etxenike arizaleta

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=CAMwawgPWu2H_M82nP93LuY-v+jVHbvax-Jppbd4pn9jPNANWoA@mail.gmail.com \
    --to=amine.aboufirass-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).