From: Ville Voipio <ville.voipio@kpatents.com>
Subject: Re: TEXMFMAIN problem in gwTeX (font installation)
Date: Mon, 02 May 2005 14:01:50 +0300 [thread overview]
Message-ID: <4276089E.80905@kpatents.com> (raw)
In-Reply-To: <4275D9B4.6040000@wxs.nl>
> generated fonts metrics are put in a given path:
And this is not the problem.
I have to apologise for the bad wording of my previous message. I am not
saying there would be anything wrong with the Perl script. The only
slight annoyance there is the error message, which states:
"unknown subpath ../fonts/afm/$vendor/$collection"
At least to my eye this seems to refer to the parent directory (..),
whereas it really doesn't. It just says that
something/something/fonts/afm/$vendor/$collection is missing. Full path
in that message would've gotten me to the goal a bit faster.
The problem is really in the font installation script (type-tmf.dat).
There the root (i.e. the source tree for the fonts) is explicitly given
as TEXMFMAIN. And this does not work in gwTeX, because if something is
given, it has to be TEXMFTE.
As a summary:
- texfont.pl is fine
- gwTeX is fine
- type-tmf.dat is not fine, but I really don't know how to reliably fix
it (yes, patching is simple, but then it does not work in other distros)
---
But am I doing something stupid (again)?
I think I have some kind of understanding of the ConTeXt font
mechanisms. However, I am still a bit confused about this mess. So, what
is the easy, standard, newbie way to install the TeX Live font
collection to be used with ConTeXt? Is it still using the type-tmf.dat
batch file?
- Ville
next prev parent reply other threads:[~2005-05-02 11:01 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
2005-05-02 11:01 ` Ville Voipio [this message]
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=4276089E.80905@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).