From: Patrick Gundlach <pg@levana.de>
Subject: box, strut
Date: Fri, 05 Sep 2003 10:01:14 +0200 [thread overview]
Message-ID: <m2d6efbr5h.fsf@levana.de> (raw)
Hello,
could someone please explain the following result?
\starttext
\setbox0=\hbox{fg}\showbox0
\setbox0=\hbox{\strut fg}\showbox0
\stoptext
gives
> \box0=
\hbox(8.33331+2.33331)x9.46518
./cmr12/f
./cmr12/g
! OK.
l.3 \setbox0=\hbox{fg}\showbox0
> \box0=
\hbox(10.41603+4.05064)x9.46518
.\hbox(10.41603+4.05064)x0.0
..\rule(10.41603+4.05064)x0.0
..\glue 0.0 plus 1.0fil minus 1.0fil
./cmr12/f
./cmr12/g
! OK.
l.4 \setbox0=\hbox{\strut fg}\showbox0
OK, the first box is easy. The second one gives me a slight headache:
why is the rule 10.4 + 4.1 pt? (14.46667 total)
the definition of strut(box) is
\setbox\strutbox=\hbox{\vrule height8.5pt depth3.5pt width\z@}
so where do the other 2.46667 point come from?
Patrick
--
Silent is the goldfish in its bowl
next reply other threads:[~2003-09-05 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 8:01 Patrick Gundlach [this message]
2003-09-05 10:23 ` Hans Hagen
2003-09-05 10:54 ` Extending into the left margin Duncan Hothersall
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=m2d6efbr5h.fsf@levana.de \
--to=pg@levana.de \
--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).