New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error:unexpected:undef Unexpected input remaining: 'undef' at pgfkeys.code.tex.ltxml; #1269
Comments
Thanks for the report @stef30360 ! Since this behaviour depends on the specific toolchain, could you also provide us with the output of:
and
Thanks! |
tex —version
TeX Live 2019/MacPorts 2019.50896_2
Latexml —version
LaTeXML version 0.8.4
OS Mojave
… Le 30 mars 2020 à 16:56, Deyan Ginev ***@***.***> a écrit :
Thanks for the report @stef30360 <https://github.com/stef30360> ! Since this behaviour depends on the specific toolchain, could you also provide us with the output of:
tex --version
and
latexml --VERSION
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1269 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUCWWA3ZP6WCGI3NOUHJ7DRKCXIHANCNFSM4LWUXTPQ>.
|
Would have been a little more informative if you pasted the full output of the commands but oh well. For now I will assume that you are working with an officially distributed 0.8.4 by a package manager? Have you tried updating to the latest master of latexml and checked if that resolves the problem? |
To speed this along, feel free to also include the full log of the conversion, and if you can a minimal example that exhibits the error. As you can imagine this type of error isn't something we can reproduce on our local installations, so the more information we gather, the better the chance we can file a patch. Thanks! |
Hi
Tku for your reply,
(Deyan edit: moving to new comment to get highlighting)
|
Thank you for the log @stef30360 , very helpful! I'm reformatting as a new comment, since github doesn't allow re-linting email replies (for reasons I don't understand for now).
|
Hi, (Deyan update: moving a minimal snippet as highlighted in the next comment) |
Thank you @stef30360 ! I minimized your snippet further, to: \documentclass{article}
\usepackage{tikz}
\usetikzlibrary{arrows}
\begin{document}
\begin{tikzpicture}[scale=1]
\draw [very thin, gray!20] (0,-6) grid[step=0.1] (12,6);
\draw [very thin, black!20] (0,-6) grid[step=0.5] (12,6);
\draw [very thin, black!40] (0,-6) grid[step=1] (12,6);
\draw[->,>=stealth] (0,0) -- (12,0) node[below right] {temps (s)};
\draw[->,>=stealth] (0,-6) -- (0,6);
\draw (1,0.1) -- (1,-0.1) node [below] {{\scriptsize $1s$}}; %échelle abscisse
\draw (0.1,1) -- (-0.1,1) node [left] {{\scriptsize $2 m/s$}}; %échelle ordonnée v
(-1.2,2.7) node [right] [red] {$V_E$};\draw [blue] (-1.8,2.2)--(-1.2,2.2) node [right] [blue] {$V_S$};
\draw[color=blue,thick,domain=0:2] plot ({\x},{1.5*\x});
\draw[color=blue,thick,domain=4:2] plot ({\x},{3});
\draw[color=blue,thick,domain=8:4] plot ({\x},{9-1.5*\x});
\draw[color=blue,thick,domain=10:8] plot ({\x},{-3});
\draw[color=blue,thick,domain=12:10] plot ({\x},{1.5*\x-18})node[above left] {$v (m/s)$};
\end{tikzpicture}
\end{document} Can you confirm you see the error here as well? The reason I can't reproduce on my machine is that you are likely using an older version of latexml and we may have already resolved this particular issue. Even with it resolved however, I am seeing the regression described in #1227 . As to the reason why it is not immediately working - latexml implements its own binding definitions that connect Tikz primitives to SVG, so it is not as robust as running I would once again recommend that you update to the latest github version of latexml and try again, but you are bound to encounter the #1227 regression if you do so before we close that issue. As things stand I can't offer you a quick solution here, apologies. |
HI |
Hm, actually, I think I was using an inconsistent local LaTeXML installation. Removing the installation directory and rebuilding, I am now seeing the following result with the latest commit 456c715 , texlive 2019: So we could consider the issue resolved for now? This is also the example discussed in #1279 which is co-resolved. |
I was alerted that I'm using texlive 2019 for these examples locally (I got mislead due to my expl3 being from early 2020, oops). And the working screenshot above is indeed with texlive 2019. Would need to get a 2020 texlive to double-check the newest state. |
Oddly, it works for me (using texlive 2020 and current latexml),
and produces plausible output.
That is excepting: no available automultiplechoice.sty, missing
meca.png, and you need a slash in `$\%$` if you want a percent.
|
Alright, sounds like both 2019 and 2020 work well at the moment in that case! (Also judging by the related #1279 ). Let's close here for now, and @stef30360 please feel free to open a new issue - or reopen this one - if you encounter more problems with pgf. latexml's support there can still be considered experimental, but we're improving gradually, as you can see from the screenshots. |
Hi,
It seem that I've problem I can convert .tex
... (Processing definitions /opt/local/share/texmf/tex/generic/pgf/utilities/pgfkeysfiltered.code.tex... 0.10 sec) 0.25 sec)
Error:unexpected:undef Unexpected input remaining: 'undef'
at pgfkeys.code.tex.ltxml; line 535
....
regards
OS+texmaker
The text was updated successfully, but these errors were encountered: