ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: Hans Hagen <pragma@wxs.nl>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: no strut in \framed
Date: Sun, 04 Sep 2011 20:23:20 +0200	[thread overview]
Message-ID: <4E63C218.8020601@gmx.net> (raw)
In-Reply-To: <4E63ABD1.4080608@wxs.nl>

Am 04.09.2011 18:48, schrieb Hans Hagen:
> On 4-9-2011 18:38, Peter Rolf wrote:
>> Hi,
>>
>> I get no strut in \framed when using 'offset=overlay' or 'offset=none'.
>>
>>
>> \setupcolors[state=start]
>> \starttext
>> \showstruts
>>
>> \framed[offset=1pt]{abc} % ok
>> \framed[offset=overlay]{abc}
>> \framed[offset=none]{abc}
>>
>> \stoptext
>>
>> Same for both marks.
> 
> indeed, and this is intentionally; use 0pt if you want a strut
>
Ok. I will add a manual '\strut' to all of my framed text elements then.
I'm forced to use 'offset=overlay' for visual debugging. The frames are
off by default, on only to control the placing/distances of the building
blocks. Using '0pt' is no option here, as this would change the object size.

Peter

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-09-04 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04 16:38 Peter Rolf
2011-09-04 16:48 ` Hans Hagen
2011-09-04 18:23   ` Peter Rolf [this message]
2011-09-04 22:39     ` Hans Hagen
2011-09-05  7:54       ` Peter Rolf

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=4E63C218.8020601@gmx.net \
    --to=indiego@gmx.net \
    --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).