-
Notifications
You must be signed in to change notification settings - Fork 14
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
Compatibility with PGF/TikZ #61
Comments
Using |
@olsak Should I try to also make PGF use the (Not sure if it is feasible, but I would like to know if this is even desirable). |
No. I think that better is the TikZ behavior like in plain TeX. |
Both ideas presented here are implemented in #63. But in the future it may be a better idea create more thorough Notably PGF uses the |
Closing (at least for now). |
With #60 we are getting more compatible with PGF/TikZ. Although we will no longer clash with the use of
\pdfpageresources
primitive token register, by either using PGF's mechanism when detected, we don't let PGF write the page resources.This is because PGF delegates the PDF object writing to
\pgfutil@everybye
and that is never executed in OpTeX (it hooks into\end
and we do\_end
).This can be mitigated manually by e.g. loading PGF/TikZ like this:
In my opinion this should be hanled by OpTeX. What about having something like
tikz.opm
that would load the real tikz and also do this? Maybe we could later include other compatibility code there (e.g. for pgf-tikz/pgf#983?). This of course bring the problem of syncing with (possible) PGF internals updates.The text was updated successfully, but these errors were encountered: