From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: experimenting metafun: problems with funnyframe
Date: Thu, 21 Dec 2000 16:42:38 +0100 [thread overview]
Message-ID: <3.0.6.32.20001221164238.01b14c60@pop.wxs.nl> (raw)
In-Reply-To: <00122113521700.00557@bilbo>
At 01:52 PM 12/21/00 +0100, Uwe Koloska wrote:
>Hans wrote on Donnerstag, 21. Dezember 2000 09:06:
>>At 05:54 PM 12/20/00 +0100, Uwe Koloska wrote:
>>>
>>>Ok, I can tweak the value since it looks right. But is it a problem of
>>>framed or funnyframe? Or is it a feature?
>>
>>It depends. I cnnot see your example, but it may be that there is a
>>dangling strut down there.
>
>Oh, it's exactly the example written down in the metafun handbook
>(27.10.2000, screen, page 196) -- I have copied the text so that there are
>no (or the same) errors in the code ...
>
>> Can you test it with
>>
>>\showstruts
>
>Where do I have to put \showstruts? I have tried the preamble, just after
>\starttext and after \startFrame -- no effect.
Well, then there are no struts interfering.
try \showstruts \strut and you see what i mean
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
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:[~2000-12-21 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 2:02 Uwe Koloska
2000-12-19 8:51 ` Berend de Boer
2000-12-19 12:26 ` S2P development
2000-12-20 2:06 ` Uwe Koloska
2000-12-19 11:10 ` Hans Hagen
2000-12-20 2:22 ` Uwe Koloska
2000-12-20 8:33 ` Hans Hagen
2000-12-20 16:54 ` Uwe Koloska
2000-12-21 8:06 ` Hans Hagen
2000-12-21 12:52 ` Uwe Koloska
2000-12-21 15:42 ` Hans Hagen [this message]
2000-12-20 17:52 ` Uwe Koloska
2000-12-21 8:16 ` Hans Hagen
2000-12-21 12:55 ` Uwe Koloska
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.20001221164238.01b14c60@pop.wxs.nl \
--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).