public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: YMALStoring bibliographic information in XML or
Date: Sun, 28 Jan 2018 11:05:54 -0800	[thread overview]
Message-ID: <20180128190554.GD80325@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <1aefef2c-ce92-4d63-a3fa-fd312ea0a999-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

You can use pandoc-citeproc to convert your .bib to a
pandoc-readable  .yaml:

    pandoc-citeproc -y my.bib > my.yaml

+++ Bruce D'Arcus [Jan 27 18 11:18 ]:
>   Pandoc can read MODS XML files.
>   I personally use biblatex these days, since it's more expressive than
>   bibtex, has good tool support (I use emacs), can be easily converted to
>   other formats (including MODS), etc.
>   On Saturday, January 27, 2018 at 7:13:33 AM UTC-5, James AUSTIN wrote:
>
>     Hi everyone
>     For years I have been storing my bibliographic information in  .bib
>     files. Unfortunately I am not finding that the .bib format is
>     particularly human readable or extensible. Looking around for
>     alternatives, I was wondering if Pandoc can read from .xml files and
>     if
>     so, how one would create a reference. I have tried to do this but
>     pandoc-citeproc tells me that my reference cannot be found. Also,
>     can
>     anyone point me in the direction of a good introduction to learning
>     YMAL
>     please, as I have seen this mentioned in the user guide as an
>     alternative to .bib.
>     Thank you.
>     Best wishes
>     James
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/1aefef2c-ce92-4d63-
>   a3fa-fd312ea0a999%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/1aefef2c-ce92-4d63-a3fa-fd312ea0a999-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2018-01-28 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27 12:13 James
     [not found] ` <36f2b28d-bd83-1ae7-36c0-cca6b74e9b1e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-27 16:00   ` John Muccigrosso
2018-01-27 19:18   ` Bruce D'Arcus
     [not found]     ` <1aefef2c-ce92-4d63-a3fa-fd312ea0a999-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-28 19:05       ` John MacFarlane [this message]
     [not found]         ` <20180128190554.GD80325-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-01-28 19:29           ` James AUSTIN

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=20180128190554.GD80325@Johns-MacBook-Pro.local \
    --to=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).