public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Any reason to keep bibliography in YAML?
Date: Mon, 21 Jun 2021 11:22:24 -0400	[thread overview]
Message-ID: <709f8eda-8625-7e29-1252-03c618931f19@reagle.org> (raw)
In-Reply-To: <m2k0mpf8jf.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>

On the formatting front, I don't have any tex math in my title, but I do have some italics.

The [json csl spec][1] says: "Note that tags must be JSON-encoded in the input object", which led me to believe that I'd have to move from:

	  "title-short": "Rewriting *The Rules*",

to

	  "title-short": "Rewriting &lt;i&gt;The Rules&lt;i&gt;"

but that doesn't work, and this does:

	  "title-short": "Rewriting <i>The Rules</i>"


[1]: https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html#html-like-formatting-tags

On 21-06-20 00:45, John MacFarlane wrote:
> There is one potentially important difference, regarding
> formatting.
> 
> CSL JSON accepts some limited formatting using HTML tags.
> 
> YAML, however, accepts the full range of Markdown formatting;
> so, for example, you can include tex math (which you can't
> do in the JSON format at present).


      parent reply	other threads:[~2021-06-21 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 19:35 Joseph Reagle
     [not found] ` <d6d1c254-27f7-32ca-e19a-2ce96fe05197-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-20  4:45   ` John MacFarlane
     [not found]     ` <m2k0mpf8jf.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-06-21 12:22       ` Joseph Reagle
2021-06-21 15:22       ` Joseph Reagle [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:
  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=709f8eda-8625-7e29-1252-03c618931f19@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).