View Issue Details

IDProjectCategoryView StatusLast Update
0000419luatexfeature requestpublic2013-12-10 11:05
ReporterTaco Assigned ToHans Hagen  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0000419: Checksum of original font files stored in the cache?
DescriptionFrom Oliver Buerschaper:

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?
Additional InformationThis needs backend support, because the frontend does not look at the actual font file, so the md5sum needs to be stored in the internal structure somewhere.
TagsNo tags attached.

Relationships

related to 0000448 closedTaco convert luafontloader returns and fonts.font[] into userdata 

Activities

Hans Hagen

2013-12-10 11:05

manager   ~0001143

some file properties are stored (already for a while) and checked when loading

Issue History

Date Modified Username Field Change
2010-06-18 09:12 Taco New Issue
2010-09-05 17:14 Taco Relationship added related to 0000448
2010-09-05 17:47 Taco Status new => assigned
2010-09-05 17:47 Taco Assigned To => Taco
2013-12-10 11:05 Hans Hagen Note Added: 0001143
2013-12-10 11:05 Hans Hagen Status assigned => closed
2013-12-10 11:05 Hans Hagen Assigned To Taco => Hans Hagen
2013-12-10 11:05 Hans Hagen Resolution open => fixed