From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: Reloading Font
Date: Sat, 12 Oct 2013 02:15:06 +0200 [thread overview]
Message-ID: <20131012001506.GC24051@tartaros> (raw)
In-Reply-To: <52589185.8080801@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1333 bytes --]
···<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.
Philipp
[-- Attachment #1.2: Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-12 0:15 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
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 [this message]
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=20131012001506.GC24051@tartaros \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--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).