From: Hans Hagen <pragma@wxs.nl>
Cc: <ntg-context@ntg.nl>
Subject: Re: mfonts
Date: Mon, 06 Aug 2001 10:03:34 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010806100130.02ac80f0@server-1> (raw)
In-Reply-To: <DFENJMIHOAJHLPPLNIINOEJNCBAA.henshr@rgsgroup.com>
At 01:48 AM 8/5/2001 -0400, Richard Hensh wrote:
>BTW, what is the proper encoding file to use?
This is a difficult question. One way to decide is to generate texnansi and
ec, and process the tex test files that are generated. If the glyphs that
you need are there it's okay, but sometimes fonts miss a couple of glyphs.
I noticed for instance funny Euro substitutions in place of ligatures in
all cap fonts (sun).
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-08-06 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 5:48 mfonts Richard Hensh
2001-08-06 8:03 ` Hans Hagen [this message]
2001-08-07 12:09 ` mfonts Richard Hensh
2001-08-08 8:37 ` mfonts Hans Hagen
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=5.1.0.14.1.20010806100130.02ac80f0@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).