On Sat, May 22, 2021 at 05:26:10PM +0200, Kornel Benko wrote: > Am Sat, 22 May 2021 16:51:43 +0200 > schrieb Jürgen Spitzmüller <sp...@lyx.org>: > > > Am Samstag, dem 22.05.2021 um 16:33 +0200 schrieb Kornel Benko: > > > Fine. But how to explain that running with 2020-dvipdfmx compiles on > > > TL20, but the same dvipdfmx (copied from TL20) fails if using TL20 env. > > > > Stricter security measures have been introduced with TL 21 [1]. > > > > The produced DVI is fine, but dvipdfmx does not produce a PDF due to > > access restrictions (when attempting to access fonts). > > > > When processing the DVI with > > > > dvipdfmx -i dvipdfmx-unsafe.cfg > > > > it works, i.e., after changing the converter DVI > PDF (dvipdfm) to > > dvipdfmx -i dvipdfmx-unsafe.cfg -o $$o $$i > > > > dvipdfmx-unsafe.cfg makes dvipdfmx call gs (rungs) with -dNOSAFER > > rather than with -DSAFER (as in the default dvipdfmx.cfg of TL21). > > Thanks. > > > However, this change should definitely only be applied to trustworthy > > files, so changing the converter generally is certainly not such a good > > idea. > > > > Jürgen > > > > [1] The explicit call of -DSAFER has been introduced for TL 21: > > https://tug.org/pipermail/tex-live-commits/2021-March/017216.html > > > > That means that we could use this setting for our tests.
Thanks for following up on this, Kornel. I think I stopped looking into this issue because I thought it was due to a known bug with a fix in progress. Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
