On 18-6-2010 9:55, Taco Hoekwater wrote:
luigi scarso wrote:
On Fri, Jun 18, 2010 at 9:40 AM, Taco Hoekwater <t...@elvenkind.com>
wrote:
Khaled Hosny wrote:
On Fri, Jun 18, 2010 at 09:10:47AM +0200, Taco Hoekwater wrote:
Oliver Buerschaper wrote:
Do you think it would be a good idea to store a checksum of the
actual font file used while generating the cache?
This sounds useful. As it will need backend support in luatex,
I will add a tracker item for this.
Isn't mtxrun --script fonts reload enough ?
Only if you actually see the problem happening, which may
not be the case. The output could be messed up without any kind of
warning from the engine.
is there unique info in the font file that we can use? version number
that is guaranteed unique? if so, we can pass that to the backend
then, if we can determine that something is wrong (a flag in
statistics), we can at the end of a run issue a message, generate that
specific font, flag the tuc file and we get a second run automatically
taco and i can discuss a few such strategies off list
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
-----------------------------------------------------------------
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
