From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3936
Path: main.gmane.org!not-for-mail
From: S2P development <taco.hoekwater@wkap.nl>
Newsgroups: gmane.comp.tex.context
Subject: Re: \blank[force] and pos-fonts
Date: Wed, 31 Jan 2001 08:39:12 +0100
Sender: owner-ntg-context@let.uu.nl
Message-ID: <3A77C120.44AD93F2@wkap.nl>
References: <3.0.6.32.20010130123807.0208ca30@server-1>
	<3.0.6.32.20010130165151.01a4e660@server-1>
	<3.0.6.32.20010130174338.013f2820@server-1>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1035394640 21460 80.91.224.250 (23 Oct 2002 17:37:20 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 17:37:20 +0000 (UTC)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:3936
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3936

Hans Hagen wrote:
> 
> Me>I'm sure you understand the basic idea behind overshoot
> Me>(the same principle as hanging punctuation).
> 
> \font\bigfont=cmr10 at 100pt \ruledhbox{o}
> 
> part of a glyph can go beyond the bbox, but do you mean that this happens
> only in cmr and that in other fonts the bbox is a real one?

Doesn't have to be this way, but it generally is. Both Type1
and TrueType allow you to define metrics independant of the
glyph shape. In 'real life' fonts though, the bounds are usually
not explicitly set by the font designer but calculated by the
font program instead. The program doesn't know the difference
between overshoots and very small descenders, so it will add
these short depths by default.

Greetings, Taco