ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rob Ermers <r.ermers@hccnet.nl>
Subject: Re: Re: using fonts -- installation
Date: Tue, 07 Dec 2004 00:19:13 +0100	[thread overview]
Message-ID: <41B4E8F1.7040602@hccnet.nl> (raw)
In-Reply-To: <20041206215016.15463@news.comp.lancs.ac.uk>

Hi Adam,

Thanks for your quick reaction. Before ending this eventful day, I ran 
texexec as you suggested.

The font in question is Hudson (vendor=softmaker = Berry 5), for which I 
  invented the name 5hu (+r for roman). I have the two files 5hur.pdf 
and 5hur.afm.

Texfont generated a number of files and put them in several directories:
- texnansi-softmaker-hudson.map in 
J:\tex\localtexmf\fonts\map\pdftex\context
- texnansi-5hur.tfm in J:\tex\localtexmf\fonts\tfm\softmaker\hudson
- texnansi-5hur.vf in J:\tex\localtexmf\fonts\vf\softmaker\hudson
- 5hur.afm in J:\tex\localtexmf\fonts\afm\softmaker\hudson
- 5hur.pfb in J:\tex\localtexmf\fonts\type1\softmaker\hudson

Texfont also generated the following:
D:\Fonts\hudson\hudson: texnansi-softmaker-hudson.log
D:\Fonts\hudson\hudson: texnansi-softmaker-hudson.tex
D:\Fonts\hudson\hudson: texnansi-softmaker-hudson.tmp
D:\Fonts\hudson\hudson: texnansi-softmaker-hudson.pdf

The pdf file does not show the hudson font - I wonder if it should.

Perhaps I should mention that Texfont was interrupted; atf2tfm gets 
stuck - a conflict with a dll, but if click on OK, nothing serious seems 
to be the matter. The tfm file is generated after all. If I test afm2tfm 
  without texfont, it works normally.

I have a test file, which is called testhuds-con.tex.

Kind regards,

Robert

  reply	other threads:[~2004-12-06 23:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 21:22 Wrap a url David Arnold
2004-11-02  9:34 ` Willi Egger
2004-11-02 14:17   ` David Arnold
2004-11-02 16:24     ` Hans Hagen
2004-11-02 17:47       ` David Arnold
2004-11-02 18:02         ` Hans Hagen
2004-12-03 14:30         ` Patrick Gundlach
2004-12-05 17:51           ` Willi Egger
2004-12-05 22:17             ` Patrick Gundlach
2004-12-06 21:19               ` Willi Egger
2004-12-05 17:52           ` Willi Egger
2004-12-06 12:40           ` using fonts Wolfgang Zillig
2004-12-06 13:41             ` Patrick Gundlach
2004-12-06 14:52               ` Adam Lindsay
2004-12-06 21:30                 ` Re: using fonts -- installation Rob Ermers
2004-12-06 21:50                   ` Adam Lindsay
2004-12-06 23:19                     ` Rob Ermers [this message]
2004-12-06 23:23                     ` h h extern
2004-12-06 23:27                   ` h h extern
2004-12-07  8:09                     ` r.ermers
2004-12-07  8:18                       ` Adam Lindsay
2004-12-07  8:17                   ` Adam Lindsay
2005-01-10 16:12               ` Problem with backgrounds and page breaks Matthias Weber
2005-01-10 17:49                 ` Hans Hagen
2005-01-10 18:35                   ` Matthias Weber
2005-01-10 18:57                     ` Hans Hagen
2005-01-10 19:29                       ` Matthias Weber
2004-12-06 14:45             ` using fonts Adam Lindsay
2004-12-06 14:50               ` Patrick Gundlach
2004-12-07  8:19 Re: using fonts -- installation Adam Lindsay

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=41B4E8F1.7040602@hccnet.nl \
    --to=r.ermers@hccnet.nl \
    --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).