From: Herbert Voss <Herbert.Voss@FU-Berlin.DE>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TYPE 1 font
Date: Thu, 11 Nov 2010 12:59:32 +0100 [thread overview]
Message-ID: <4CDBDAA4.2060602@FU-Berlin.DE> (raw)
In-Reply-To: <AANLkTimthyn9vZ=om_Ek-1qtuRrhZw+DYRuBV8=Yws+s@mail.gmail.com>
Am 11.11.2010 12:10, schrieb Mojca Miklavec:
> 2010/11/11 Herbert Voss wrote:
>> Does ConTeXt always needs an afm-file for the metrics of an
>> type 1 font? And, of course, a map file?
>
> Shouldn't DANTE launch a pet project and convert the font to OpenType?
> (That should be 10-60 minutes of work for somebody familiar with
> fonts.)
>
> But yes, as Hans replied, you need afm file. pdfTeX gets all the font
> metric data from tfm files, while ConTeXt MKIV prefers to be able to
> use more than 256 characters when they are available in Type1 font (it
> doesn't need or read enc, map, vf and tfm files).
thanks,
I converted it with fontforge to otf. Now I get
voss@shania:/opt/context> mtxrun --script fonts --list --all
--pattern=*dante*
dante dante DANTE.otf
dantenormal dante DANTE.otf
Is this the intended behaviour, that the afm files are now no
more listed? without the otf version the output is:
voss@shania:/opt/context> mtxrun --script fonts --list --all
--pattern=*dante*
dante dante dante.afm
dantenormal dante dante.afm
Herbert
___________________________________________________________________________________
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:[~2010-11-11 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 8:16 Herbert Voss
2010-11-11 8:56 ` Hans Hagen
2010-11-11 11:10 ` Mojca Miklavec
2010-11-11 11:59 ` Herbert Voss [this message]
2010-11-11 12:03 ` Hans Hagen
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=4CDBDAA4.2060602@FU-Berlin.DE \
--to=herbert.voss@fu-berlin.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).