From: Hans Hagen <pragma@wxs.nl>
Subject: Re: mfonts.tex from manuals
Date: Wed, 23 Nov 2005 11:47:35 +0100 [thread overview]
Message-ID: <438448C7.3090203@wxs.nl> (raw)
In-Reply-To: <438419D2.1060904@elvenkind.com>
Taco Hoekwater wrote:
> 1. Certainly the *easiest* way to get a working solution is to
> change the fontsynonyms in typ-dis.tex so that they match the real
> world instead of the desired world.
in the past we have cycled between both [u|p]plr8t kind of names and the
problem was that
(1) sometimes one of them was missing
(2) this aliasses file (obscure kpse feature) was interfering
(3) the location of files changed [this urw35v thing] resulting in
missed files while copying
for instance, it was always a gamble what reference to the dingbats
would work today
so
>
> 2. But on the other hand, that would be promoting a rather bad
> practise, and deleting the fontsynonyms instead would be better.
this looks like the way to go
>
> I happen to know that Hans will start distributing a cont-fnt.zip
> file soon that will contain texfont-style metrics, so my vote goes
> to the second solution.
that makes two votes ...
Hans
next prev parent reply other threads:[~2005-11-23 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 23:27 David Arnold
2005-11-23 7:27 ` Taco Hoekwater
2005-11-23 10:47 ` Hans Hagen [this message]
2005-11-23 15:14 ` Adam Lindsay
2005-11-25 1:37 ` David Arnold
2005-11-25 10:41 ` Adam Lindsay
2005-11-25 19:27 ` David Arnold
2005-11-25 20:14 ` Hans Hagen
2005-11-25 20:26 ` David Arnold
2005-11-25 22:42 ` Gerben Wierda
2005-11-25 23:35 ` Henning Hraban Ramm
2005-11-25 23:58 ` Adam Lindsay
2005-11-26 0:41 ` Hans Hagen
2005-12-01 19:16 ` Hans Hagen
2005-12-01 1:45 ` David Arnold
2005-12-06 14:20 ` Mojca Miklavec
2005-12-06 16:13 ` Hans Hagen
[not found] <20051207133722.90749.qmail@web54404.mail.yahoo.com>
2005-12-09 13:04 ` Mojca Miklavec
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=438448C7.3090203@wxs.nl \
--to=pragma@wxs.nl \
--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).