From: Hans Hagen <pragma@wxs.nl>
To: "Reviczky, Adam" <adam.reviczky@kcl.ac.uk>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Error with export=yes
Date: Mon, 09 May 2011 15:01:43 +0200 [thread overview]
Message-ID: <4DC7E5B7.10009@wxs.nl> (raw)
In-Reply-To: <7B4626C28B06A7418E938BF73D6DEE18F9F571EC99@KCL-MAIL05.kclad.ds.kcl.ac.uk>
On 9-5-2011 2:53, Reviczky, Adam wrote:
>> no clue
>
> So it looks like having the urw zapfding fonts from texlive mess this up (uzdr.afm, uzdr.pfb and uzdr.pfm).
> Don't you have them? Why is it a problem if context finds those?
>
> Without those fonts, I have this in the log:
>
> fonts> names> font database has matching configuration and file hashes
> fonts> defining> font with asked name 'dingbats' is not found using lookup 'name'
> fonts> defining> unknown font dingbats, loading aborted
> fonts> defining> unable to define dingbats as \**currentsymbolfont**
> fonts> names> font database has matching configuration and file hashes
> fonts> defining> font with asked name 'dingbats' is not found using lookup 'name'
> fonts> defining> unknown font dingbats, loading aborted
> fonts> defining> unable to define dingbats as \**currentsymbolfont**
> fonts> names> font database has matching configuration and file hashes
> fonts> defining> font with asked name 'dingbats' is not found using lookup 'name'
> fonts> defining> unknown font dingbats, loading aborted
> fonts> defining> unable to define dingbats as \**thedefinedfont**
i use a system font
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-05-09 13:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 2:57 Reviczky, Adam
2011-05-09 11:24 ` Hans Hagen
2011-05-09 11:32 ` Reviczky, Adam
2011-05-09 11:52 ` Hans Hagen
2011-05-09 12:53 ` Reviczky, Adam
2011-05-09 13:01 ` Hans Hagen [this message]
2011-05-09 15:12 ` Hans Hagen
2011-05-09 15:28 ` Reviczky, Adam
2011-05-09 16:48 ` Reviczky, Adam
2011-05-09 16:55 ` Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2011-05-09 17:05 Reviczky, Adam
2011-05-09 17:30 ` Reviczky, Adam
2011-05-09 17:45 ` Reviczky, Adam
2011-05-09 20:01 ` Hans Hagen
2011-05-07 0:57 Reviczky, Adam
2011-05-07 10:24 ` Hans Hagen
2011-05-09 2:13 ` Reviczky, Adam
2011-05-06 13:39 Aditya Mahajan
2011-05-06 14:07 ` Hans Hagen
2011-05-06 14:45 ` Aditya Mahajan
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=4DC7E5B7.10009@wxs.nl \
--to=pragma@wxs.nl \
--cc=adam.reviczky@kcl.ac.uk \
--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).