On 3/26/2020 10:25 AM, The Thanh Han wrote:
On Wed, Mar 25, 2020 at 2:18 PM Hans Hagen
mailto:j.hagen@xs4all.nl> wrote: On 3/25/2020 2:06 PM, The Thanh Han wrote: > Hi Karl, > > it seems the primary problem is that pdftex tries to set font expansion > parameters for a font without checking if the font has been > successfully loaded (hence it modifies null_font which is totally wrong). > > Please find the proposed patch attached. I have tested it against your > test files (thanks again for making things easy to reproduce). But shouldn't there be some message then too?
I agree clear message should be given when something goes wrong. In this case however I don't know what message should pdftex say. The fix is about preventing pdftex from doing something it should not, i.e. setting expansion parameters for a font that could not be loaded.
something "no expansion applied to virtual font 'foo'" or so ... just to prevent some question about a possible bug coming up 5 years from now (when everyone has forgotten about this check) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------