From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: A new metafont (beta test)
Date: Sun, 11 Mar 2001 22:25:52 +0100 [thread overview]
Message-ID: <3.0.6.32.20010311222552.01a43100@server-1> (raw)
In-Reply-To: <3AA17F78.D5CDDCAC@quicknet.nl>
At 12:34 AM 3/4/01 +0100, you wrote:
> http://www.elvenkind.com/~taco/elogo/elogo.zip
Ah, bitmap fonts.
(1) somehow ljfour is not known, what should i change add ?
(2) when i run 'm and get 2602 files i don't get tfm's
So, what I did was:
mpost -ini &mfplain \dump
move the mem to the web2cpath
mpost &mfplain elogo10
mpost &mfplain elogobf10
mpost &mfplain elogod10
mpost &mfplain elogosl10
mpost &mfplain elogosl9
mpost &mfplain elogo8
mpost &mfplain elogo9
mpost &mfplain elogoslbf10
texexec --fig=c elogo* --pdf
and voila, got 'm, so making type 1 should be possible since the glyphs
look okay.
Some chars have a nice subtle curvature, i assume you went to the max in
that. Nice. The imaginary low x height was probably a strong driving force.
I think that in general the chars are nice, but i'm not sure about the oe
ligature and the &. Also, the 3 is the only one with a small hook left/top
(straight line would be better).
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-03-11 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 23:34 Taco Hoekwater
2001-03-04 13:27 ` Taco Hoekwater
2001-03-11 21:25 ` Hans Hagen
2001-03-14 0:13 ` Re[2]: " Giuseppe Bilotta
2001-03-14 9:35 ` Hans Hagen
2001-03-11 21:25 ` Hans Hagen [this message]
2001-03-13 9:03 ` S2P development
2001-03-13 9:15 ` Hans Hagen
2001-03-14 14:16 ` Denis B. Roegel
2001-03-14 14:55 ` S2P development
2001-03-14 19:29 ` Denis B. Roegel
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=3.0.6.32.20010311222552.01a43100@server-1 \
--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).