On Fri, Jun 18, 2010 at 10:36:36AM +0200, Hans Hagen wrote: > On 17-6-2010 11:54, Oliver Buerschaper wrote: > >Dear wise guys, > > > >the other day I found myself caught in a trap that might be a frequent > >source of puzzlement for the casual ConTeXt user :-) > > > >I had replaced an OpenType font in the usual OS directory by a new version. > >Typesetting documents using that font produced surprising results... the PDF > >files were merrily messed up. I reckon I didn't pay attention to the > >interplay between font files and the LuaTeX cache... apparently ConTeXt was > >using the outdated font cache data together with the new font file since a > >few days later the problem was resolved once I had to regenerate the cache > >for other reasons. Only then did I notice I had also cured this font problem. > > > >Do you think it would be a good idea to store a checksum of the actual font > >file used while generating the cache? > > no, as calculating the checksum is quite slow > > normally context will detect a change in filesize so i wonder what > went wrong at your end
File size is not reliable, I do frequently change fonts and context doesn't reload the font, so I have to delete the cache by hand. -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer _______________________________________________ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
