From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: no color after LaTeX -> docx
Date: Tue, 21 Nov 2023 23:30:05 -0500 [thread overview]
Message-ID: <D0F89010-268E-4F66-85D0-82196CA5FF53@gmail.com> (raw)
In-Reply-To: <82960ecf-864e-4379-9726-303997983cebn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Pandoc doesn't support color.
> On Nov 21, 2023, at 3:45 AM, 姜政毅（贪吃的小神仙） <doctorjzy@gmail.com> wrote:
>
> I am trying to convert latex to docx with pandoc.
>
> LaTeX code is very simple:
>
> \documentclass{article}
> \usepackage{xcolor}
> \begin{document}
> This is a \textcolor{blue}{blue} word.
> \end{document}
>
> And I convert it to docx by command
> pandoc -s file.tex -o file.docx
>
> But file.docx do not have color. Can anybody tell me what is going on here?
>
> --
> 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/82960ecf-864e-4379-9726-303997983cebn%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/D0F89010-268E-4F66-85D0-82196CA5FF53%40gmail.com.
prev parent reply other threads:[~2023-11-22 4:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 8:45 姜政毅（贪吃的小神仙）
[not found] ` <82960ecf-864e-4379-9726-303997983cebn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-21 10:49 ` Bastien DUMONT
2023-11-21 11:37 ` 'William Lupton' via pandoc-discuss
[not found] ` <CAEe_xxicy9Np+9vktAPtnfaAhHg4sopkgT21+_oQSHV0jgdgVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-21 12:11 ` Bastien DUMONT
2023-11-22 4:36 ` John MacFarlane
[not found] ` <2FA49E21-A3FD-449E-9292-F18ECEAC4291-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-11-22 12:20 ` 'William Lupton' via pandoc-discuss
2023-11-22 4:30 ` 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=D0F89010-268E-4F66-85D0-82196CA5FF53@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).