ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Cc: ntg-context@ntg.nl
Subject: Re: Going crazy with font conversion (diaeresis)!
Date: Tue, 22 Mar 2005 17:14:47 +0100	[thread overview]
Message-ID: <a06210201be65f2819d99@[62.134.76.149]> (raw)

Hi Adam,


Adam Lindsay <atl@comp.lancs.ac.uk> wrote:

>  Okay, it was trickier than I thought.
>  But I used the .afm obtained from FontForge conversion, and discarded
>  the .pfb.
>
>    afm2pl -p `kpsewhich texnansi.enc` HelveticaNeue.afm
>    pltotf HelveticaNeue
>
>  Because I'm impatient, and wanted a quick test:
>  \loadmapline[+HelveticaNeue HelveticaNeue " TeXnANSIEncoding
>  ReEncodeFont " <texnansi.enc <HelveticaNeue.ttf]
>  \starttext
>  \definedfont[HelveticaNeue]
>  TAVAT.Po
>  T{}A{}V{}A{}T{}.{}P{}o
>  \stoptext


Your result looks promising - but duplicating your way showed me my 
command line limits:

$ afm2pl -p `kpsewhich texnansi.enc` HelveticaNeue.afm
afm2pl: fatal: default.lig not found.

$ pltotf HelveticaNeue
pltotf: HelveticaNeue.pl: No such file or directory

As I have never used afm2pl or pltotf the usage above is praobably wrong.
Or was my Fontforge export bad?
(When I open the AFM exported by FontForge there are no entries for 
KerningPairs ...)

And looking at your test file: where are your ttf and other files in 
this situation?

Steffen

             reply	other threads:[~2005-03-22 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 16:14 Steffen Wolfrum [this message]
2005-03-22 16:47 ` Adam Lindsay
2005-03-23 18:57   ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2005-03-22 20:40 Steffen Wolfrum
2005-03-23 11:29 ` Adam Lindsay
2005-03-22 16:23 Steffen Wolfrum
2005-03-22 12:03 Steffen Wolfrum
2005-03-22 14:43 ` Adam Lindsay
2005-03-22 14:54 ` Ulrich Dirr
2005-03-22 15:19   ` Adam Lindsay
2005-03-21 15:37 Steffen Wolfrum
2005-03-21 16:38 ` Adam Lindsay
2005-03-21 18:13 ` Patrick Gundlach

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='a06210201be65f2819d99@[62.134.76.149]' \
    --to=context@st.estfiles.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).