Re: Experimental citeproc implementation in Rust

[John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>]

Cormac Relf <web-v7Sng7lNsVbsQp/K+IV0sw@public.gmane.org> writes:

> The BibTex parsing is a tricky one, though. There’s this 
> <https://github.com/charlesvdv/nom-bibtex> for the main syntax, at least. I 
> wouldn’t want to fork out to Pandoc for every single latex text field, but 
> maybe the Lua API’s read would help here.

That's an interesting point.  If your parser just
parsed the fields as RawInline (Format "latex") ---,
you could have the lua filter do a separate pass at
the beginning to try to convert all of these into
native pandoc inlines using read.

> It might be simpler to support 
> both citeproc-js’ micro-HTML and a similarly limited micro-LaTeX with a 
> simple Rust-based parser, but not at the same time. What do people use 
> backslash commands for in BibTeX? Are there names and document titles out 
> there that really need the whole power of LaTeX to render? I might have to 
> think about this some more. Perhaps a successor to CSL-JSON that accepts 
> arbitrary JSON objects wherever the old one accepts strings.

In practice, a fairly small subset of LaTeX would be
enough to handle most of what you find in bibtex
bibliographies.

Certainly you will find things like `\emph`, inline
math, and lots of escape characters like `\"{a}`.

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/yh480kk1keeazt.fsf%40johnmacfarlane.net.
For more options, visit https://groups.google.com/d/optout.