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:36:40 -0500 [thread overview]
Message-ID: <2FA49E21-A3FD-449E-9292-F18ECEAC4291@gmail.com> (raw)
In-Reply-To: <CAEe_xxicy9Np+9vktAPtnfaAhHg4sopkgT21+_oQSHV0jgdgVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Well, after saying that pandoc doesn't support color, I saw this. You're right, this seems to be something the LaTeX reader does.
% pandoc -f latex -t native
\documentclass{article}
\begin{document}
\textcolor{blue}{blue}
\end{document}
[ Para
[ Span
( "" , [] , [ ( "style" , "color: blue" ) ] ) [ Str "blue" ]
]
]
Looks like this goes back to commit d9439808f2fe226aad027c8c9d0a38217a1e8c34 in 2017.
I don't think I ought to have merged this change -- this is too HTML-centric for the LaTeX reader to be producing.
> On Nov 21, 2023, at 6:37 AM, 'William Lupton' via pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
>
> It seems that the LaTeX reader encodes the color info in a style attribute? (try.pandoc)
>
> \documentclass{article}
> \begin{document}
> \textcolor{blue}{blue}
> \end{document}
>
> -->
>
> <p><span style="color: blue">blue</span></p>
next prev parent reply other threads:[~2023-11-22 4:36 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 [this message]
[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
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=2FA49E21-A3FD-449E-9292-F18ECEAC4291@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).