Am 20.06.2025 um 15:18 schrieb John Was:
Dear Wolfgang
The hyphenation exceptions look much more complicated than my simple file - but at any rate it can't be that that's causing all this processing time.
Here is the result of the mtxrun command you sent:
identifier familyname fontname filename subfont instances
baskervillemtprobold baskervillemtpro baskervillemtprobold c:/windows/fonts/BaskervilleMTPro-Bold.otf baskervillemtproboldit baskervillemtpro baskervillemtproboldit c:/windows/fonts/BaskervilleMTPro-BoldIt.otf baskervillemtprobolditalic baskervillemtpro baskervillemtproboldit c:/windows/fonts/BaskervilleMTPro-BoldIt.otf baskervillemtproitalic baskervillemtpro baskervillemtproitalic c:/windows/fonts/BaskervilleMTPro-Italic.otf baskervillemtpronormal baskervillemtpro baskervillemtproregular c:/windows/fonts/BaskervilleMTPro-Regular.otf baskervillemtproregular baskervillemtpro baskervillemtproregular c:/windows/fonts/BaskervilleMTPro-Regular.otf
I don't think that ConTexT is repeatedly searching for Baskerville in particular (though after just a few days I can't claim any expertise in reading ConTexT log files). But it does seem to want to survey the entire database of fonts, whether or not I need them.
I don't know if it would help to call a font specifically from its file location, which I have occasionally had to do for exotic sorts that are rarely required, e.g. (from my days of typesetting the /Medieval Latin Dictionary from British Sources/), in XeTeX style:
\font\mldrten="[D:/BACKUPS/FONTBKUP/MLD/MLD-Regular.ttf]" at 10pt
Does it make a differenece if you typeset a simple document with the baskerville fonts \starttext \definedfont[file:BaskervilleMTPro-Regular.otf*default] Hello \CONTEXT! \stoptext or the default latin modern fonts? \starttext Hello \CONTEXT! \stoptext Wolfgang