From: h h extern <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
TeX on Mac OS X Mailing List <MacOSX-TeX@email.esm.psu.edu>
Subject: Re: TEXMFMAIN problem in gwTeX (font installation)
Date: Mon, 02 May 2005 09:41:40 +0200 [thread overview]
Message-ID: <4275D9B4.6040000@wxs.nl> (raw)
In-Reply-To: <797c87f1126c1c8a1cab222b37735652@rna.nl>
Gerben Wierda wrote:
> 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.
generated fonts metrics are put in a given path:
if (defined($ENV{TEXMFLOCAL})) {
$installpath = "TEXMFLOCAL" ;
}
if (defined($ENV{TEXMFFONTS})) {
$installpath = "TEXMFFONTS" ;
}
if ($installpath eq "") {
$installpath = "TEXMFLOCAL" ; # redundant
}
and later on
my $fontroot = "" ; #/usr/people/gwhite/texmf-fonts"
&GetOptions
"fontroot=s" => \$fontroot,
and
if ($fontroot eq "")
{ if ($dosish)
{ $fontroot = `kpsewhich -expand-path=\$$installpath` }
else
{ $fontroot = `kpsewhich -expand-path=\\\$$installpath` }
chomp $fontroot }
etc etc
I've added texmfdist to the search trees list
my $trees = 'TEXMFFONTS,TEXMFLOCAL,TEXMFEXTRA,TEXMFMAIN,TEXMFDIST' ;
(not that i use dist: the first thing i do here when i get tex live is merging
the main/dist/doc/extra trees)
btw, it's interesting that when i asked for a texmffonts entry long ago the
argument against was 'we don't want too many trees' but nowadays we have so many
trees that i no longer feel trouble by my own amount:
texmf
texmf-extra
texmf-local
texmf-fonts
texmf-projects
texmf-mswin
texmf-macosx
texmf-linux
etc -)
normally i try to use kpse to locate and report paths, but this is kind of slow
and the kpsewhich interface is not frozen [which is why in more recent scripts i
use a wrapper system around kpse, so in the end such problems may disappear]
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-05-02 7:41 UTC|newest]
Thread overview: 8+ 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 ` [NTG-context] " Gerben Wierda
2005-05-02 7:41 ` h h extern [this message]
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=4275D9B4.6040000@wxs.nl \
--to=pragma@wxs.nl \
--cc=MacOSX-TeX@email.esm.psu.edu \
--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).