From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Failed to convert markdown with latex to docx
Date: Mon, 21 Nov 2022 19:27:54 -0800 [thread overview]
Message-ID: <554C26C7-5761-4F3A-B966-6494A50C35BD@gmail.com> (raw)
In-Reply-To: <19d69c0f-a719-4308-9793-c75cc38a038fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
As it says: \enspace isn't recognized.
That needs to be fixed in the texmath library.
You can submit a bug report at
https://github.com/jgm/texmath/issues
In the mean time, you can work around this by including
\renewcommand{\enspace}{\hspace{0.5em}}
in your document, before this part.
> On Nov 21, 2022, at 6:29 PM, swhoro <swhoro404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Part of my md file:
>
> $$
> APP:\ <MS\_SET,\enspace MS_{RELATION}>
> $$
>
>
> using this command:
>
> pandoc -f markdown+latex_macros -t docx -o my.docx .\Untitled-1.md
>
> error report:
>
> [WARNING] Could not convert TeX math
> APP:\ <MS\_SET,\enspace MS_{RELATION}>
> , rendering as TeX:
>
> ^
> unexpected control sequence \enspace
> expecting "%", "\\label", "\\tag", "\\nonumber" or whitespace
>
>
> --
> 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/19d69c0f-a719-4308-9793-c75cc38a038fn%40googlegroups.com.
next prev parent reply other threads:[~2022-11-22 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 2:29 swhoro
[not found] ` <19d69c0f-a719-4308-9793-c75cc38a038fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-22 3:27 ` John MacFarlane [this message]
[not found] ` <554C26C7-5761-4F3A-B966-6494A50C35BD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-22 7:04 ` swhoro
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=554C26C7-5761-4F3A-B966-6494A50C35BD@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).