ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ville Voipio <ville.voipio@kpatents.com>
Subject: RE: TEXMFMAIN problem in gwTeX (font installation)
Date: Mon, 2 May 2005 20:18:34 +0300	[thread overview]
Message-ID: <98D0564335EC4848A87BEDEFF4EA056B55BC@posti.kpatents.com> (raw)

> Just for my understanding. Does texfont.pl only
> read in TEXMFMAIN or does it also write (can it
> be a search path or does it require for TEXMFMAIN
> to be just one directory)?

texfont.pl checks several places. By a very quick look
at the sources, it looks for the following:

  TEXMFMAIN
  TEXMFLOCAL
  TEXMFEXTRA
  TEXMFFONTS

It does not look for TEXMFTE, but by specifying the
switch --rootlist, it can be given a list of trees,
which it then browses through.

Ok, it might be useful to add a few here, such as
TEXMFTE (for us gwTeX users), but maybe that's an
endless road. But the real problem is really in a
font installation script which explicitly overrides
the default settings and gives a wrong tree.

---

The problem is easy to pinpoint into type-tfm.dat.
Unfortunately, just removing the explicit definitions
does not seem to solve the problem. The non-standard
root seems to be difficult to be told to the system.

For encodings, texfont.pl can be force-fed a value
which is passed to all scripts in a batch file (using
a special --en=? switch). However, no such mechanism
exists for other parameters (such as the --ro).

Tweaking the TEXMFFONTS to point to TEXMFTE is one
possibility, but then the fonts will also be installed
into TEXMFFONTS instead of TEXMFLOCAL.

Ideally, it would be nice to be able to tell the
script that the source fonts are in TEXMFWHATEVER
and they are going into TEXMFSOMETHINGELSE. I haven't
been able to figure out how to achieve that without
tailoring the batch file.

- Ville

             reply	other threads:[~2005-05-02 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 17:18 Ville Voipio [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-29 13:03 Ville Voipio
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

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=98D0564335EC4848A87BEDEFF4EA056B55BC@posti.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).