ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <Gerben.Wierda-ORJpgvefH5M@public.gmane.org>
Cc: TeX on Mac OS X Mailing List
	<MacOSX-TeX-yNUTs0qEFpZ/1wmUHrjjoYdd74u8MsAO@public.gmane.org>
Subject: Re: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
Date: Sun, 1 May 2005 11:28:02 +0200	[thread overview]
Message-ID: <797c87f1126c1c8a1cab222b37735652@rna.nl> (raw)
In-Reply-To: <427230A6.6080500-oEVuXQnkYvdWk0Htik3J/w@public.gmane.org>

On Apr 29, 2005, at 15:03, Ville Voipio wrote (on the ConTeX list, but 
this also is interesting for all gwTeX users):

> 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)?

TEXMFMAIN in TL is now reserved for only the stuff that is directly 
related to the binaries (like the pool files or anything that needs to 
stay in sync - grammar wise - with the binaries and scripts). In TeX 
Live the 'foundation' now lives in .../texmf-dist (TEXMFDIST) and not 
in ../texmf

In gwTeX, there are a few foundation trees: TEXMFTE for the teTeX tree 
and TEXMFGW for my additions

I think it is a simplification by texfont that it has a hardwired 
location. TeX is not set up that way. Probably the correct solution is 
for texfont itself to act in a more dynamic way, e.g. by trying to 
locate with kpsewhich some elements that are supposed to be there 
already and take th eresult of that search as the settin for what it 
now assumes to be hardwired.

In the meantime: your fix is correct.

G

--------------------- Info ---------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
           & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Post: <mailto:MacOSX-TeX-yNUTs0qEFpZ/1wmUHrjjoYdd74u8MsAO@public.gmane.org>




  parent reply	other threads:[~2005-05-01  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 13:03 Ville Voipio
     [not found] ` <427230A6.6080500-oEVuXQnkYvdWk0Htik3J/w@public.gmane.org>
2005-05-01  9:28   ` Gerben Wierda [this message]
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=797c87f1126c1c8a1cab222b37735652@rna.nl \
    --to=gerben.wierda-orjpgvefh5m@public.gmane.org \
    --cc=MacOSX-TeX-yNUTs0qEFpZ/1wmUHrjjoYdd74u8MsAO@public.gmane.org \
    /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).