From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: wrong vertical spacing in latest beta
Date: Thu, 16 Apr 2015 22:38:56 +0200 [thread overview]
Message-ID: <55301DE0.4080704@wxs.nl> (raw)
In-Reply-To: <5530197B.70609@gmx.es>
On 4/16/2015 10:20 PM, Pablo Rodriguez wrote:
> On 04/16/2015 09:51 PM, Hans Hagen wrote:
>> On 4/16/2015 6:50 PM, Pablo Rodriguez wrote:
>>> [...]
>>> I’m afraid it might be a bug.
>>
>> hm, more likely a fix (prevdepth or so)
>>
>> \startbuffer[a]
>> \ruledvbox{x\tfa \setupinterlinespace \strut \ConTeXt \par
>> \strut x\par}\blank
>> \ruledvbox{x\tfxx\setupinterlinespace \strut Author \par
>> \strut x\par}\blank
>> \ruledvbox{x\tfxx\setupinterlinespace \strut \currentdate \par
>> \strut x\par}\blank
>> \ruledvbox{x\tf \setupinterlinespace \strut url \par
>> \strut x\par}\blank
>> \stopbuffer
>>
>> \startbuffer[b]
>> \ruledvbox{x\tfa \setupinterlinespace \ConTeXt \par
>> x\par}\blank
>> \ruledvbox{x\tfxx\setupinterlinespace Author \par
>> x\par}\blank
>> \ruledvbox{x\tfxx\setupinterlinespace \currentdate \par
>> x\par}\blank
>> \ruledvbox{x\tf \setupinterlinespace url \par
>> x\par}\blank
>> \stopbuffer
>>
>> \starttext
>> \showstruts
>> \getbuffer[a]
>> \page
>> \getbuffer[b]
>> \stoptext
>>
>> you can use use \begstrut ... \endstrut in such local situations
>
> Many thanks for your help, Hans.
>
> I have seen strut in the past, but I’m afraid that I don’t know what it
> may be or what I can use it for (besides your sample).
tex has no built-in concept of lineheight and depth only of distance
so, if you want consistency you need to make sure the first line has
height and the last line depth
for normal running text this goes ok (thanks to baselineskip being the
sum of wanted height and depth)
but ... as soon as you start boxing you need to make sure you enforce
the proper ht and dp is needed
\begstrut ... \endstrut
can be used for that
most mechanisnm in context deal with this themselves (for instance
framed and tables .. tables would look horrible otherwise)
(try \showstruts before \starttext so see where \struts are used)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-04-16 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 16:50 Pablo Rodriguez
2015-04-16 19:51 ` Hans Hagen
2015-04-16 20:20 ` Pablo Rodriguez
2015-04-16 20:38 ` Hans Hagen [this message]
2015-04-16 21:16 ` Pablo Rodriguez
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=55301DE0.4080704@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).