ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ville Voipio <ville.voipio@kpatents.com>
Subject: TEXMFMAIN problem in gwTeX (font installation)
Date: Fri, 29 Apr 2005 16:03:34 +0300	[thread overview]
Message-ID: <427230A6.6080500@kpatents.com> (raw)

I have spent some very interesting time trying to install the TeXlive 
fonts by using texfont type-tmf.dat. What happened was that a lot of 
complaints about "unknown subpath ../afm/public/urw" were given even 
though the path should have been there. This is a known problem, has 
been on several mailing lists, as well.

After a lot of thinking it became clear that texfont was really unable 
to find any font files. By browsing through the texfont.pl, the reason 
became evident: In gwTeX the root variables are:

    TEXMFMAIN = /usr/local/teTeX/share/texmf
    TEXMFTE = /usr/local/teTeX/share/texmf.tetex

The problem here is that all the TeXlive fonts (and almost everthing 
else) is really in the TEXMFTE tree.

My quick'n'dirty was to make new file type-tmf-gwtex.dat by replacing 
all occurrences of TEXMFMAIN by TEXMFTE. Running that one in batch mode 
works fine.

Problem solved -- this time. But the solution is not a beautiful one. 
Could someone suggest something cleaner? Or has this been solved already 
(I tried googling after the answer without success)?

- Ville

             reply	other threads:[~2005-04-29 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 13:03 Ville Voipio [this message]
     [not found] ` <427230A6.6080500-oEVuXQnkYvdWk0Htik3J/w@public.gmane.org>
2005-05-01  9:28   ` [NTG-context] " Gerben Wierda
2005-05-02  7:41     ` h h extern
2005-05-02 11:01       ` Ville Voipio
2005-05-02 15:10         ` Gerben Wierda
2005-05-02 15:22           ` Adam Lindsay
2005-05-02  7:47     ` h h extern
2005-05-02 17:18 Ville Voipio

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=427230A6.6080500@kpatents.com \
    --to=ville.voipio@kpatents.com \
    --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).