ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nigel King <king@dircon.co.uk>
Subject: Re: texfont and type-tmf.dat
Date: Thu, 09 Oct 2003 18:31:49 +0100	[thread overview]
Message-ID: <BBAB5A15.16AD6%king@dircon.co.uk> (raw)
In-Reply-To: <m2zngaogxs.fsf@levana.de>

All,
I hadn't expected to create such a confusion so I will try to restate my
problem.

On MacOSX Gerben has provided a restructured version of tetex where the
locations of some files have changed. I am not sure of the detailed reasons
for this but it certainly much easier to keep up to date. For instance he
even provides an updater for ConTeXt to beta or standard using a single
click (I only just found that! Thanks Gerben).

Now the line 
 texfont --en=8r --ve=urw --co=courier --so=auto
Should work but instead gives

 TeXFont 1.8 - ConTeXt / PRAGMA ADE 2000-2003

    processing aborted : unknown subpath ../fonts/afm/urw/courier

The subpath exists but maybe at a different root
/usr/local/teTeX/share/texmf.tetex/fonts/afm/urw/courier
thus I presume that --fontroot should be invoked especially since the help
gives me 
  --fontroot=path : texmf font root (default:
/usr/local/tetex/share/texmf.local)
So I try 
texfont --en=8r --ve=urw --co=courier --so=auto
--fontroot=/usr/local/teTeX/share/texmf.tetex/
on one line of course

    processing aborted : unknown subpath ../fonts/afm/urw/courier
is the result.

The apparent error is that the --fontroot option doesn't work. Hopefully
that is all I wanted fixed. Texfont has been upgraded with many new options
but this 'bug' remains.

TIA
-- 
Nigel

  reply	other threads:[~2003-10-09 17:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAA1DC4D.ECA9%king@dircon.co.uk>
2003-08-06 20:21 ` Nigel King
2003-08-06 22:05   ` Gerben Wierda
2003-08-07  6:42     ` Nigel King
2003-08-08  0:31       ` darnold
2003-08-08  1:14         ` Trouble with updated Context darnold
     [not found]       ` <1591.209.209.17.128.1060305294.squirrel@webmail.inreach.co m>
2003-08-08  7:47         ` Hans Hagen
     [not found]     ` <1516.209.209.15.183.1060302710.squirrel@webmail.inreach.co m>
2003-08-08  7:48       ` texfont and type-tmf.dat Hans Hagen
2003-08-11 13:00     ` Hans Hagen
2003-10-08 17:14       ` Nigel King
2003-10-08 17:32         ` Patrick Gundlach
2003-10-08 17:59           ` Nigel King
2003-10-08 18:13             ` Patrick Gundlach
2003-10-08 22:04               ` Hans Hagen
2003-10-09  9:00                 ` Patrick Gundlach
2003-10-09  9:23                   ` Hans Hagen
2003-10-09 10:15                     ` Patrick Gundlach
2003-10-09 17:31                       ` Nigel King [this message]
2003-10-09 18:52                         ` Patrick Gundlach
2003-10-14 21:48                           ` Nigel King
2003-10-14 22:14                             ` Patrick Gundlach
2003-10-14 22:58                               ` Nigel King
2003-10-14 23:04                                 ` Patrick Gundlach
2003-10-14 23:27 George N. White III
2003-10-14 23:46 ` Patrick Gundlach
  -- strict thread matches above, loose matches on Subject: below --
2003-10-10 17:38 George White
2003-10-10 20:21 ` Patrick Gundlach
2003-08-03  5:37 Matthew Huggett
2003-08-03  5:57 ` David Arnold
2003-08-04  8:14 ` 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=BBAB5A15.16AD6%king@dircon.co.uk \
    --to=king@dircon.co.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).