On Fri, Jun 18, 2010 at 10:16 AM, Oliver Buerschaper <oliver.buerscha...@mpq.mpg.de> wrote: >>> 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. >> I mean: one should not simply copy an opentype font into (context) >> system and expected things to work. >> Checksum should be check at every runs, which is useless most of the time: >> in a production env. I don't change fonts for long time , and every >> change is tested. >> Maybe a lua script to install fonts is better -- we can eventually >> think to a wxLua gui interface .
> I'm not sure. In a desktop environment the user will just update the OpenType > font via the OS (e.g. replace a file in the usual OS font directory). From > that moment on the font will work in almost any application... don't you > think it's reasonable to just have the updated font work in ConTeXt, too? >Addendum: should an updated font not work out of the box (i.e. change the >looks of an existing document) then I think the usual DTP suspects issue a >warning. hm,no as general rule. I prefer to separate context issue from OS issue, just to be sure that I can move my projects in whatever OS I have Also a fonts can not be "good" for context (missing something), but can be ok for OS, and I don't want that an OS upgrade the font that is also used by potentially different projects -- each project has it own sets of fonts and I decide what to share, not the OS. In this way I can also work with linux winxp seven etc without problems. -- luigi _______________________________________________ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
