ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Charles <ce@vejnar.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Linebreak in a framed for a chapter setuphead
Date: Wed, 29 Feb 2012 16:28:36 +0100	[thread overview]
Message-ID: <4F4E4424.20903@vejnar.org> (raw)
In-Reply-To: <26500510-46A7-4A14-98E4-F122BAC16923@googlemail.com>

Le 29/02/2012 16:18, Wolfgang Schuster a écrit :
>
> Am 29.02.2012 um 16:05 schrieb Charles:
>
>> Le 29/02/2012 12:42, Wolfgang Schuster a écrit :
>>>
>>> Am 29.02.2012 um 12:19 schrieb Charles:
>>>
>>>> Hi,
>>>>
>>>> I have a problem with the following definition of chapter header. I would like to have the chapter title on the left side and the number, with higher size, on the right side.
>>>>
>>>> The \mychap seems to work while used directly.
>>>>
>>>> Any solution?
>>>
>>> \define[2]\mychap
>>>    {\framed
>>>       [frame=off,width=broad,align=flushleft,bottomframe=on,offset=0pt]
>>>       {\setbox\scratchbox\hbox{#1}%
>>>        \vtop{\hsize\dimexpr\hsize-\wd\scratchbox\relax#2}%
>>>        \box\scratchbox}}
>>>
>>> \setuphead[chapter][command=\mychap,textstyle=\tfa,numberstyle=\tfd]
>>>
>>> \starttext
>>>
>>> \chapter{INTRODUCTION}
>>>
>>> \chapter{Text and more text and even more text and still more text till it stops}
>>>
>>> \stoptext
>>>
>>> Wolfgang
>>
>> Thanks Wolfgang.
>>
>> How is the position of the text controled inside the framed? I would like it to be closer to the line (when I increase the font size the space between the text and the line increases too much).
>
> You can set “strut=no” and use the “depth” parameter.
>
> \define[2]\mychap
>   {\framed
>     %[frame=off,width=broad,align=flushleft,bottomframe=on,offset=0pt]
>      [frame=off,width=broad,align=flushleft,bottomframe=on,offset=0pt,strut=no,depth=0.4ex]
>      {\startlocalheadsetup
>       \setbox\scratchbox\hbox{\setnostrut#1}%
>       \vtop{\hsize\dimexpr\hsize-\wd\scratchbox\relax#2}%
>       \box\scratchbox
>       \stoplocalheadsetup}}
>
> \setuphead[chapter][command=\mychap,textstyle=\tfa,numberstyle=\tfd,strut=no]
>
> \starttext
>
> \chapter{INTRODUCTION}
>
> \chapter{Text and more text and even more text and still more text till it stops}
>
> \stoptext
>
> Wolfgang

Perfect! Thank you very much

Charles

___________________________________________________________________________________
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:[~2012-02-29 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 11:19 Charles
2012-02-29 11:42 ` Wolfgang Schuster
2012-02-29 15:05   ` Charles
2012-02-29 15:18     ` Wolfgang Schuster
2012-02-29 15:28       ` Charles [this message]

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=4F4E4424.20903@vejnar.org \
    --to=ce@vejnar.org \
    --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).