Hi Henri
>
> \documentclass{article}
> \usepackage{xcolor}
> \begin{document}
> \textcolor{gray!100}{Lorem ipsum.}
> \end{document}
>
There is a bug in tex4ht color support which causes a compilation
error when the color name is same as a color scheme name. You would
get the same error with \text
Workaround:
\documentclass{article}
\usepackage{xcolor}
\begin{document}
\textcolor{gray!100}{Lorem ipsum.}
\end{document}
On 9/04/19 9:06 AM, Henri Menke wrote:
> Thank you Karl, but that has nothing to do with the TeX4ht problems.
>
> I was able to fix the first problem by simply moving the \d
Thank you Karl, but that has nothing to do with the TeX4ht problems.
I was able to fix the first problem by simply moving the \definecolor outside
of \AtBeginDocument. Now I have another problem, illustrated by the following
MWE. This works all nice and fine with my default engine LuaTeX, but fa
This particular construction is actually part of the PGF/TikZ manual
and currently prevents the manual from typesetting.
FWIW, I just reverted pgf in TeX Live to its previous release. -k
On 4/8/2019 1:45 AM, Michal Hoftich wrote:
Hi Nasser, Bill,
This sounds like a good solution. I do not know if those in the know-how
could implement this in ex4ht if it not too hard.
I also do not know if I could do what you described using some configuration
in my .cfg.
You can put this \Cs
