From: Henning Hraban Ramm <angerweit@gmx.net>
Subject: Re: font check
Date: Mon, 1 Jul 2002 19:13:37 +0200 [thread overview]
Message-ID: <200207011913.37065.angerweit@gmx.net> (raw)
In-Reply-To: <p0510030fb9451e47fe64@[172.16.22.38]>
Am Sonntag, 30. Juni 2002 22:50 schrieb Axel Rose:
> I was trying to follow your instuctions and set TEXMF, etc.
> and nothing works any longer.
Maybe my suggestions work only for my modified teTeX on SuSE.
Grüßlis vom Hraban!
next prev parent reply other threads:[~2002-07-01 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 15:45 Axel Rose
2002-06-30 16:31 ` Bill McClain
2002-06-30 18:47 ` Axel Rose
2002-06-30 20:19 ` Henning Hraban Ramm
2002-06-30 20:50 ` Axel Rose
2002-07-01 17:13 ` Henning Hraban Ramm [this message]
2002-06-30 20:38 ` Bill McClain
2002-06-30 19:36 ` fonts and tetex Glenn R. Williams
2002-06-30 20:45 ` Bill McClain
2002-06-30 21:16 ` Axel Rose
2002-06-30 23:03 ` fonts and tetex - partial success! Glenn R. Williams
2002-07-01 11:35 ` Bill McClain
2002-07-01 14:50 ` fonts and tetex - partial success! (more info on stops) Glenn R. Williams
2002-07-01 17:10 ` fonts and tetex - partial success! Henning Hraban Ramm
2002-07-01 19:45 ` John Culleton
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=200207011913.37065.angerweit@gmx.net \
--to=angerweit@gmx.net \
/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).