From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: TeX Live 2019 / TikZ
Date: Mon, 09 Sep 2019 16:41:00 -0000 [thread overview]
Message-ID: <5f6e2df1-48f0-eaf5-9f54-2aef49f09fad@SystematicSw.ab.ca> (raw)
In-Reply-To: <87r24qc65q.fsf@Rainer.invalid>
On 2019-09-09 00:53, Achim Gratz wrote:
> Ken Brown writes:
>> I had a chance to take a quick look, and this is a known problem:
>
> Thanks, I hadn't found this for whatever reason.
>
>> https://tex.stackexchange.com/questions/473365/why-is-pgf-3-1-not-compatible-with-tex
>>
>> I suspect there's been a new release of PGF that fixes this. I'll check on it
>> and release an appropriate update when I return home.
>
> It's been fixed here:
> https://github.com/pgf-tikz/pgf/issues/508
That was reverted as closed won't fix and they said - users *MUST NOT* have
*ANY* unnecessary spaces in the definitions of math functions, such as prior to
comments!
> But the main issue really is that TikZ/PGF need eTeX to work correctly
> (the fix above to work with plain TeX loses functionality). Indeed, if
> I change the test in question to use etex, it passes. I'll report that
> upstream as a bug in the test driver (it shouldn't assume that tex or
> latex really is an eTeX variant).
ε-Τeχ is now assumed as the default engine by all current formats and packages
except Plain Τeχ, and required for future development as it expands all fixed
register counts from 256 to 32K.
[There looks to be an opportunity for a gΤeχ that removes all arbitrary
limitations, probably imposed because of SAIL or Pascal limitations in original
implementations.]
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-09-09 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 10:59 Achim Gratz
2019-09-08 13:20 ` Ken Brown
2019-09-09 6:53 ` Ken Brown
2019-09-09 12:00 ` Achim Gratz
2019-09-09 16:41 ` Brian Inglis [this message]
2019-09-13 19:05 ` Ken Brown
2019-09-14 12:42 ` Achim Gratz
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=5f6e2df1-48f0-eaf5-9f54-2aef49f09fad@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).