On 10/12/2013 12:26 AM, Philipp Gesang wrote:
···<date: 2013-10-11, Friday>···<from: Thangalin>···
FYI,
I didn't know that the font was corrupt. I have over 400 fonts on my
machine, and had to reload to pick up the new ones. You'll find that
having a large number of fonts will start to become a common situation
as more fonts become public (e.g., Google's Free Web Fonts project).
This increases the chances that some of those fonts will be corrupt.
sure, but fonts should be chosen with care .. and illegal ripoffs should
be avoided (those cd's with hundreds of fonts, nowadays sites)
(quality of design / digitization, completeness of coverage, correctness
of features ... much can be wrong)
It is a low priority, but a corrupt font should not cause a program to
hang or crash. The software should exit gracefully, and perhaps
strongly suggest to standard error that the user investigate that
particular font file.
+1
For my particular application, eventually I will allow users to upload
custom fonts. If they upload a font that is corrupt (accidentally or
intentionally), a run-away process would make for a rainy day.
In that case I'd run a separate font checker, as you never know what
users upload. Similar issues can occur with those tagged formats that
are in fact linked lists.
That’s a serious problem with Luatex. The fontforge libraries
used to import font data simply hang with various corrupt fonts.
So far the only viable workaround is to manually create a
blacklist of bad fonts. E.g. this is the current list for
Luaotfload:
https://github.com/lualatex/luaotfload/blob/master/luaotfload-blacklist.cnf
(Copperplate is going to be added soon.) Unfortunately, Context
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.
a slippery road .. blacklisting .. this is why it's todo .. (actually in
the beginning context had something like that) ... the problem is that
such lists can be persistent and users don't know about them
(anyhow, I enabled it in the treatments but probably am not going to
waste much time on such fonts ... a font not loading is one, but in
order to be complete blacklisting would also need to involve fonts with
bugged encodings - and i've seen some - and other issues ... i also want
to avoid a 'why doesn't this font work, it should because it's not
blacklisted' kind of discussions)
Regards,
Philipp
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
--
-----------------------------------------------------------------
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
