![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
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 Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------