ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: Leah Neukirchen <leah@vuxu.org>
Subject: Re: LMTX incompatibility in \meaning breaks TikZ, other minor issues
Date: Thu, 29 Sep 2022 00:29:41 +0200	[thread overview]
Message-ID: <87h70rjfoq.fsf@vuxu.org> (raw)
In-Reply-To: <20160ed8-603f-c392-66af-a92d52d4c6ba@xs4all.nl>

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  <leah@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
___________________________________________________________________________________

      reply	other threads:[~2022-09-28 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 12:23 Leah Neukirchen via ntg-context
2022-09-22 17:40 ` Hans Hagen via ntg-context
2022-09-28 22:29   ` Leah Neukirchen via ntg-context [this message]

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=87h70rjfoq.fsf@vuxu.org \
    --to=ntg-context@ntg.nl \
    --cc=leah@vuxu.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).