From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: raw_tex commands substitution with bibtex input
Date: Wed, 8 Mar 2023 21:52:25 -0800 [thread overview]
Message-ID: <6DE91339-D332-4DCB-833F-1CECE1DFFB67@gmail.com> (raw)
In-Reply-To: <c6cfd247-822c-419e-a8ec-e3cee10e03f0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
We should probably enable raw_tex for bibtex input. Feel free to raise an issue on the tracker for this.
> On Mar 8, 2023, at 4:48 PM, bapt a <auguieba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hi,
>
> I'm not sure how to approach this: suppose I want to produce html output from a .bib file uses LaTeX commands such as `\textregistered`, or `\myname` as an alias, etc. but outside a math environment (`$\textregistered$` would be fine, as it's handled as Inline Math and passed to mathjax).
>
> With a different input format, I could use the `+raw_tex` extension to make sure pandoc does not drop the latex commands, and have a Lua filter perform the desired substitutions, as in this answer: https://stackoverflow.com/a/56391373
>
> Unfortunately, I'm getting this message from pandoc: "The extension raw_tex is not supported for bibtex"
>
> Is there a workaround for such substitutions?
>
> Many thanks,
>
> baptiste
>
>
> ---
> pandoc test.bib --from bibtex+raw_tex -t csljson -o test.json
>
> sample bibtex
>
> @preamble{"\providecommand{\textregistered}{\unicode{xAE}}"}
> @preamble{"\providecommand{\customalias}{Akshay Agrawal}"}
>
> @article{agrawal2021mde,
> author = {\customalias and Alnur Ali and Stephen Boyd},
> doi = {10.1561/2200000090},
> journal = {Foundations and Trends{\textregistered} in Machine Learning},
> number = {3},
> pages = {211--378},
> publisher = {Now Publishers},
> title = {Minimum-Distortion Embedding},
> url = {https://doi.org/10.1561/2200000090},
> volume = {14},
> year = {2021},
> bdsk-url-1 = {https://doi.org/10.1561/2200000090}}
>
>
>
>
> --
> 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/c6cfd247-822c-419e-a8ec-e3cee10e03f0n%40googlegroups.com.
--
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/6DE91339-D332-4DCB-833F-1CECE1DFFB67%40gmail.com.
prev parent reply other threads:[~2023-03-09 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 0:48 bapt a
[not found] ` <c6cfd247-822c-419e-a8ec-e3cee10e03f0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-09 5:52 ` John MacFarlane [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=6DE91339-D332-4DCB-833F-1CECE1DFFB67@gmail.com \
--to=fiddlosopher-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).