ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: Reloading Font
Date: Fri, 11 Oct 2013 08:55:38 +0200	[thread overview]
Message-ID: <CAG5iGsAHMmo6xSmxjznyb7R4UEM0m9iTM35kPAa6aj-Den7LKg@mail.gmail.com> (raw)
In-Reply-To: <CAANrE7pDMtjz+YtoQGNUz=ONVcTeF-Z=Ox_tKZYzU+252Sv2NA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 884 bytes --]

On Fri, Oct 11, 2013 at 5:35 AM, Thangalin <thangalin@gmail.com> wrote:

> Hi,
>
> A font causes mtxrun to hang upon reloading. Replicate:
>
> mkdir $HOME/.fonts
> cd $HOME/.fonts
> wget http://whitemagicsoftware.com/Copperplate-ThirtyThreeBC.ttf
> export OSFONTDIR=$HOME/.fonts
> mtxrun --script fonts --reload
>
> Expected Results
>
> All the fonts in $HOME/.fonts and subdirectories are globbed and
> imported, within a few seconds.
>
> Actual Results
>
> The program hangs at Copperplate 33BC font with the CPU locked at
> 100%. The process must be killed.
>
I have not downloaded the file
but you can try copying the font file into a local folder like
texmf-project/test
together with this test.tex

\starttext
 \definedfont[./Copperplate-ThirtyThreeBC.ttf<http://whitemagicsoftware.com/Copperplate-ThirtyThreeBC.ttf>
]
 \input knuth
\stoptext

and see what happens



-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 1603 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
___________________________________________________________________________________

  reply	other threads:[~2013-10-11  6:55 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 [this message]
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
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=CAG5iGsAHMmo6xSmxjznyb7R4UEM0m9iTM35kPAa6aj-Den7LKg@mail.gmail.com \
    --to=luigi.scarso@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).