From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: vertical position of framed sucks!
Date: Fri, 29 Aug 2008 10:36:56 +0200 [thread overview]
Message-ID: <0C71A21F-AFC8-45E0-8195-7B1960B3AF3E@st.estfiles.de> (raw)
In-Reply-To: <48B7ACFB.2020700@gmx.net>
Hi,
sorry for my foggy post last night (02:50h ...)
Hopefully this example makes it clearer:
--
\starttext
\showframe
\definehead[EbeneFuenf] [subsubsubsection]
\setupsection[section-6][conversion=characters,previousnumber=yes]
\def\FuenfCommand#1{#1.}
\def\CurrentEbeneFuenfNumber#1#2%
{\hbox to \hsize\bgroup%
\tbox{\midaligned
\framed[offset=-0.5pt,frame=on,align=middle,width=0.85\textwidth]
{{\FuenfCommand{\convertnumber{characters}
{\countervalue{@@sesection-6}}}}{\kern0.75em}#2}}%
\egroup}
\setuphead[EbeneFuenf][command=\CurrentEbeneFuenfNumber]% using this
command moves the line 2mm down?!
\EbeneFuenf{Test}
\stoptext
--
I wanted to define a command with a fixed width in order to determine
a maximum width for a section.
But using this command (i.e. the "framed") also moves the section down
about 2mm!
How can this be avoided?
Steffen
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-08-29 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 0:46 Steffen Wolfrum
2008-08-29 7:40 ` Hans Hagen
2008-08-29 8:02 ` Peter Rolf
2008-08-29 8:36 ` Steffen Wolfrum [this message]
2008-08-29 9:18 ` Peter Rolf
2008-08-29 9:33 ` Steffen Wolfrum
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=0C71A21F-AFC8-45E0-8195-7B1960B3AF3E@st.estfiles.de \
--to=context@st.estfiles.de \
--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).