Hi Hans, On Thu, 2026-03-19 at 14:12 +0100, Hans Hagen via ntg-context wrote: > On 3/19/2026 10:43 AM, Max Chernoff via ntg-context wrote: > > - The pragmatist: I only have free fonts installed, and my friend send > > me a .tex file that depends on non-free fonts. If I rename some free > > fonts without .lfg files to the same name as the proprietary fonts, > > then the document compiles correctly; therefore, the type-imp-* files > > are useful on their own without proprietary software. But this > > renaming trick gives an error with the .lfg files (or produces > > unusable output, etc.), therefore these files are not useful with only > > free software. > > > > - The literalist: type-imp-* files are like .map files, therefore they > > are allowed. .lfg files are like .tfm files, therefore they are not > > allowed. > > Yes, see the long explanation above :). But please let me know if > > anything is still unclear, and I can try and clarify it further. > > Well, I strongly suggest that if the needed lfg files are not there, > then the typescript files should also not be there. So: just remove the > cambria files from tex live then.
I already did that last year: any type-imp-* files that depend on excluded .lfg files are also excluded. > We just don't want to deal with this > kind of inconsistencies: it just doesn't pass our quality criteria and > in fact works against quality. The rename or copy some whatever font to > cambria is imo rediculous. 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. > If that fails somehow in a run, so be it: a > missing file is something we can explain, inconsistent and crappy output > is much harder, unless we no longer care. We spent a lot of time on > these math issues. 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. > 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. Thanks, -- Max ___________________________________________________________________________________ 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 ___________________________________________________________________________________
