[NTG-context] Bug: Reloading Font

Philipp Gesang Philipp.Gesang at alumni.uni-heidelberg.de
Sat Oct 12 02:15:06 CEST 2013

···<date: 2013-10-12, Saturday>···<from: Hans Hagen>···

> On 10/12/2013 12:48 AM, Thangalin wrote:
> > Hi
> >
> >> (Copperplate is going to be added soon.) Unfortunately, Context
> >
> > Keep in mind it was only Copperplate 33 BC. Also note that I could not
> > find any version of Copperplate 33 BC online that had the same file
> > size as my corrupt version. (I was trying to find the source of the
> > corrupt copy.)
> >
> > Most other copies, I'd imagine, are fine, so don't be too quick to blacklist it.
> indeed, and when you don't notice that it's blacklisted, it can happen 
> that this one instance gets unnoticed
> >> does not yet have blacklisting functionality (it’s marked as todo
> >> in the source) so you’re going to have to filter out bad files
> >> from your font directories by hand.
> >
> > Sounds like the real solution is to fix fontforge so that it doesn't hang.
> sure, although a crash has the nice advantage of knowing that a font 
> (collection) is crap (which i then can blacklist permanently in my mind)

Sure, but there’s a difference between a crash and a freeze. The
latter can be quite annoying for those who work with strange
editors that run TeX somewhere in the background making it
impossible to kill the process using Ctrl-C.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://www.ntg.nl/pipermail/ntg-context/attachments/20131012/79876b53/attachment-0001.pgp>

More information about the ntg-context mailing list