From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: Reloading Font
Date: Fri, 11 Oct 2013 14:39:38 -0700 [thread overview]
Message-ID: <CAANrE7oCnwBqW6Qpqqz_amV_Pf-B9LAsM11Poz1wi62-EWa=rw@mail.gmail.com> (raw)
In-Reply-To: <52586AB6.6030302@wxs.nl>
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.
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.
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.
Kindest regards.
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-10-11 21:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 3:35 Thangalin
2013-10-11 6:55 ` luigi scarso
2013-10-11 7:59 ` Hans Hagen
2013-10-11 8:59 ` luigi scarso
2013-10-11 11:55 ` luigi scarso
2013-10-11 12:02 ` Taco Hoekwater
2013-10-11 15:19 ` Thangalin
2013-10-11 21:16 ` Hans Hagen
2013-10-11 21:39 ` Thangalin [this message]
2013-10-11 22:26 ` Philipp Gesang
2013-10-11 22:48 ` Thangalin
2013-10-12 0:02 ` Hans Hagen
2013-10-12 0:15 ` Philipp Gesang
2013-10-12 0:19 ` Hans Hagen
2013-10-12 7:27 ` Khaled Hosny
2013-10-12 9:18 ` Hans Hagen
2013-10-12 10:19 ` Khaled Hosny
2013-10-12 22:39 ` Hans Hagen
2013-10-13 8:15 ` Khaled Hosny
2013-10-13 9:49 ` Hans Hagen
2013-10-13 11:48 ` luigi scarso
2013-10-11 23:53 ` Hans Hagen
2013-10-12 3:05 ` Thangalin
2013-10-12 8:52 ` Khaled Hosny
2013-10-12 9:20 ` Hans Hagen
2013-10-12 9:29 ` luigi scarso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAANrE7oCnwBqW6Qpqqz_amV_Pf-B9LAsM11Poz1wi62-EWa=rw@mail.gmail.com' \
--to=thangalin@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).