Hi Max,
I already did that last year: any type-imp-* files that depend on
excluded .lfg files are also excluded.
ok, so consistent
I don't expect anyone to ever do that, and I don't think that anyone
_should_ ever do that, but the fact that it's theoretically possible was
one of the ways that I was able to justify the policy change.
ok (not that the policy change affected us, as the typescripts without
pfg are useless; i assume these huge latex files with non free fonts
mentioned were the reason for the policy change, the saving time etc
argument)
I believe that I had already excluded the relevant type-imp-* from my
initial release (or in the first update a few days later), so for as
long as I've been responsible for the packaging, the ConTeXt in TL has
never distributed type-imp-* files with missing .lfg files, meaning that
the font rendering will either be fully correct, or loading the font
will fail completely.
good
An alternative is a more strick consistency test and let context crash
on a file when this kind of hackery happens.
I believe that that's what happens already, but my memory might be wrong
here.
no need to recover memory
Thanks,
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : [email protected] /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
