From: Hraban <angerweit@gmx.net>
Subject: Fonts (Was: compilation is stuck!)
Date: Tue, 07 Nov 2000 19:54:57 +0100 [thread overview]
Message-ID: <3A084FFF.724715EE@gmx.net> (raw)
In-Reply-To: <3.0.6.32.20001105215246.01b4be90@pop.wxs.nl>
Hans Hagen wrote:
> >That solved my fonts problems -- e.g. my teTeX distrib lacked
> >the *8t.* files for Palatino, that's why mktextfm was called
> >and failed.
> Right, i still don't know what palatino names to take. Maybe taco knows the
> definitive answer to that.
I liked to use the Adobe Palatino (also because they're built in PS
printers),
but my try to convert the MacOS fonts to Linux/Windows pfbs failed
(wrong enc?),
so I do now use the URW Palladio -- it's free, and the quality seems ok.
I'd suggest you set preferences to the free URW PS fonts that come also
with Ghostscript.
Ehm, if the fonts are under the GPL (and not GPLL) -- must I put all
TeX "source code" that uses them under GPL? What abaout the printed
products?
BTW:
I was surprised not to find TeX files for Berkeley (pby) on CTAN.
Seems I must make it myself. (Berkeley OS italic is my "corporate font").
---
Grüßlis vom Hraban!
---
http://angerweit.tikon.ch/lieder/
http://www.planet-interkom.de/fiee.visuelle/formelsammlung.html
next prev parent reply other threads:[~2000-11-07 18:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 12:15 compilation is stuck! Denis B. Roegel
2000-11-02 12:28 ` Hans Hagen
2000-11-03 15:31 ` Denis B. Roegel
2000-11-03 15:49 ` Ed L Cashin
2000-11-03 15:58 ` Denis B. Roegel
2000-11-03 16:10 ` Ed L Cashin
2000-11-03 16:16 ` Denis B. Roegel
2000-11-03 16:55 ` Hans Hagen
2000-11-03 19:27 ` Denis B. Roegel
2000-11-03 16:57 ` Hans Hagen
2000-11-03 19:45 ` Denis B. Roegel
2000-11-04 15:15 ` Hraban
2000-11-05 20:52 ` Hans Hagen
2000-11-06 15:47 ` Taco Hoekwater
2000-11-07 18:54 ` Hraban [this message]
2000-11-05 20:18 ` Hans Hagen
2000-11-08 12:37 ` compilation is stuck! (problems with postscript fonts on unix) Uwe Koloska
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=3A084FFF.724715EE@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).