From: "j. van den hoff" <veedeehjay@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Hans Hagen" <pragma@wxs.nl>
Subject: Re: fluctuating baseline of header text
Date: Sun, 28 Dec 2014 12:39:50 +0100 [thread overview]
Message-ID: <op.xrktcojnp7eajd@muck.fritz.box> (raw)
In-Reply-To: <549F449C.1040804@wxs.nl>
On Sun, 28 Dec 2014 00:45:32 +0100, Hans Hagen <pragma@wxs.nl> wrote:
> -- could such behaviour be achieved presently with some clever trick?
>
> \showstruts
> \setuppagenumbering[style=\bfd\setcharstrut{0123456789}\strut,strut=no]
> - no default strut
> - calculate one based on to-be-used-characters (tight case)
> - apply that one
>
> compare it with
> \setuppagenumbering[style=\bfd\setstrut\strut]
>
thanks a lot. that indeed fixes it.
> And then wikify it
can do. although things are not yet 100% clear to me (not much to be found
in the documentation). so is this right:
-- I guess `\setstrut\strut' does set the strut to the maximum height of
all the glyphs in the used font? the explanation in 4.6 of the ref. manual
is not really telling me how the box height in the example comes about
(i.e. what the mentioned `maximal height' actually is).
-- `\setcharstrut{0123456789}': the command seems to be completely
undocumented (I could not find it in wiki and ref. manual), but it seems
clear what it does. except what do you mean by "tight case" here?
-- why is it necessary to state `strut=no' to switch of the default on top
of setting the strut explicitly?
joerg
> Hans
>
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___________________________________________________________________________________
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:[~2014-12-28 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 22:32 j. van den hoff
2014-12-27 9:40 ` Pablo Rodriguez
2014-12-27 11:16 ` j. van den hoff
2014-12-27 12:36 ` Hans Hagen
2014-12-27 14:07 ` j. van den hoff
2014-12-27 14:10 ` j. van den hoff
2014-12-27 15:35 ` j. van den hoff
2014-12-27 23:45 ` Hans Hagen
2014-12-28 11:39 ` j. van den hoff [this message]
2014-12-28 17:55 ` Hans Hagen
2014-12-28 18:08 ` j. van den hoff
-- strict thread matches above, loose matches on Subject: below --
2014-12-26 22:30 j. van den hoff
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=op.xrktcojnp7eajd@muck.fritz.box \
--to=veedeehjay@googlemail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).