Hans Hagen via ntg-context <ntg-context@ntg.nl> writes: >> After a bunch of debugging, it turns out that LMTX breaks the TikZ >> 'quotes' >> library, which works using code ala: >> \def\tikz@enable@node@quotes{% >> \pgfkeyssetvalue{/handlers/first char syntax/the character >> "}{\tikz@quote@parser}% >> \let\tikz@quotes@as\tikz@node@quotes@as% >> } >> The last part of the /-key is derived from \meaning, but in LMTX, >> \meaning" is "the character U+0022 'quotation mark'" >> and thus the key cannot be found. >> I have patched TikZ for now to match for this alternate string too. > > a bit weird way to test a key .. maybe you can compare to > > \edef\ThatQuote{\meaning/} > > using \ifx > >> But perhaps it would be better for compatibility to agree with the >> original TeX \meaning strings for the 7-bit ASCII subset at least. > > too messy when want to parse
To follow up on this: I have upstreamed patches to tikz and tikz-cd to use the dynamic output of \meaning instead of hardcoding. I'm not sure who maintains the t-tikz module, but if it gets updated at some point the fix should be in. -- Leah Neukirchen <l...@vuxu.org> https://leahneukirchen.org/ ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________