From: "Peter Münster" <pmlists@free.fr>
Cc: Hans Hagen <pragma@wxs.nl>, Hartmut Henkel <hartmut_henkel@gmx.de>
Subject: Re: [Fwd: Re: [Fwd: HZ and DVI]]
Date: Tue, 09 Jan 2007 21:20:51 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0701092117220.26974@gaston.pm> (raw)
In-Reply-To: <Pine.LNX.4.64.0701092020250.3095@hahepc1.hahe>
On Tue, 9 Jan 2007, Hartmut Henkel wrote:
> ok, no bug). I hope that Peter Münster, who was always in the Cc:, now
> knows what to do if he still wants to use HZ in DVI files. In short, he
> would need to generate all required expanded .tfm files (if not in
> autoexpand mode) and .pk fonts by hand with proper expanded naming,
> using e. g. mktextfm and gsftopk or mktexpk tools. But it's nowadays
> much much easier to do HZ in PDF mode.
Indeed, I'll go the easy way: I'll try to forget all about dvi and go pdf.
Thank you for all your investigations!
Cheers, Peter
--
http://pmrb.free.fr/contact/
prev parent reply other threads:[~2007-01-09 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 0:05 Hans Hagen
2007-01-09 19:29 ` Hartmut Henkel
2007-01-09 20:20 ` Peter Münster [this message]
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=Pine.LNX.4.58.0701092117220.26974@gaston.pm \
--to=pmlists@free.fr \
--cc=hartmut_henkel@gmx.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).