From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: \blank[force] and pos-fonts
Date: Tue, 30 Jan 2001 12:38:07 +0100 [thread overview]
Message-ID: <3.0.6.32.20010130123807.0208ca30@server-1> (raw)
In-Reply-To: <01012919465200.03930@bilbo>
At 07:46 PM 1/29/01 +0100, Uwe Koloska wrote:
>Hello,
>
>I have found a very annoying problem:
>
>\setupbodyfont[ber,pos,sans]
>
>\starttext
>Hallo?
>\page
>\blank[force,4*big]
>Hallo, erstmal!
>\stoptext
>
>There is no topspace at the second page. After removing "pos" from
>\setupbodyfont[ber,sans] there is.
>
>What's going on there? It has nothing to do with "pos" itself since if I
>include my own postscript font there is the same behaviour.
>
>pdfeTeX, Version 3.14159-14e-released-20000217-2.1 (Web2C 7.3.1)
>ConTeXt ver: 2001.1.19 fmt: 2001.1.23 int: english mes: english
>
>nothing unusal (AFAIK) in .log.
Interesting. At the top of the page prevdepth = .12pt in pos fonts
[probably delta topskip/strutheight or so].
In main-001.tex you may change (search for \ifblankforceer):
\ifblankoforceer
% -1000pt signals top of page or column (\ejectcolumn)
\vbox{\strut}\kern-\lineheight
\fi
Since [given its usage] no additional testing is needed.
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-01-30 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 18:46 Uwe Koloska
2001-01-30 10:55 ` Is \em font-dependent? Michal Kvasnicka
2001-01-30 12:31 ` Hans Hagen
2001-01-30 11:38 ` Hans Hagen [this message]
2001-01-30 14:18 ` \blank[force] and pos-fonts S2P development
2001-01-30 15:51 ` Hans Hagen
2001-01-30 16:17 ` Taco Hoekwater
2001-01-30 16:43 ` Hans Hagen
2001-01-31 7:39 ` S2P development
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.20010130123807.0208ca30@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).