We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some TikZ libraries (e.g. quotes) use keys which include the string given by \meaning, e.g.
quotes
\meaning
\pgfkeyssetvalue{/handlers/first char syntax/the character "}{\tikz@quote@parser}%
However, in LMTX, \meaning" expands to
\meaning"
the character U+0022 'quotation mark'
and they don't intent to change that.
In my experiments, it seems sufficient to instead write
\pgfkeyssetvalue{/handlers/first char syntax/\meaning"}{\tikz@quote@parser}%
which uses whatever string the current TeX implementation uses.
This is related to #990.
(this is ConTeXt)
\usemodule[tikz] \usetikzlibrary[quotes,angles] \starttext \meaning" \starttikzpicture \node ["abc" draw] {node}; \stoptikzpicture \stoptext
The text was updated successfully, but these errors were encountered:
0280303
I think we need \expandafter\meaning\string" here, just in case " is active at that point.
\expandafter\meaning\string"
"
Sorry, something went wrong.
Also in
pgf/tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibraryanimations.code.tex
Line 597 in 0280303
Thanks for the quick fixing!
fix: guard against LuaMetaTeX's changed \meaning
4f0b709
Fixes pgf-tikz#1193 Co-authored-by: Leah Neukirchen <leah@vuxu.org>
No branches or pull requests
Brief outline of the bug
Some TikZ libraries (e.g.
quotes
) use keys which include the string given by\meaning
, e.g.However, in LMTX,
\meaning"
expands toand they don't intent to change that.
In my experiments, it seems sufficient to instead write
which uses whatever string the current TeX implementation uses.
This is related to #990.
Minimal working example (MWE)
(this is ConTeXt)
The text was updated successfully, but these errors were encountered: