From: Taco <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: strange
Date: Wed, 8 May 2002 10:51:41 +0200 [thread overview]
Message-ID: <20020508105141.2e5796f6.taco@elvenkind.com> (raw)
In-Reply-To: <87sn53dpj6.fsf@gundla.ch>
On 08 May 2002 10:14:53 +0200
"Patrick Gundlach" <pg@levana.de> wrote:
> > I maybe wrong but it looks like glyphs have different dimensions in
> > different encodings:
> >
> > \hbox
> > {\font\test=uplr8t \test \ruledhbox{t}
> > \font\test=uplr8r \test \ruledhbox{t}}
>
>
> that is what I have found in the tfm files:
Heights and depths are often rounded somewhat because there are not
that many distinct values that can be saved in a TFM file.
Different encoding usually equals different glyphs, and therefore
different rounding errors. The width usually does not have that problem,
since more values can be saved and characters usually don't change
width when an accent is added.
prev parent reply other threads:[~2002-05-08 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 19:09 strange Hans Hagen
2002-05-08 8:14 ` strange Patrick Gundlach
2002-05-08 8:51 ` Taco [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=20020508105141.2e5796f6.taco@elvenkind.com \
--to=taco@elvenkind.com \
--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).