ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Part head centering and empty header
Date: Wed, 03 May 2006 21:57:24 +0200	[thread overview]
Message-ID: <44590B24.4090303@wxs.nl> (raw)
In-Reply-To: <E1Fabnq-0007Mx-00@smtp06.web.de>

Johannes Graumann wrote:
> John R. Culleton wrote:
>
>   
>> I would take a different approach, with each part header (there
>> can't be that many) enclosed in
>> \startstandardmakeup
>> and
>> \stopstandardmakeup
>>
>> To get the part into the TOC there is a command to write an
>> entry manually, with \writetolist.
>>     
>
> Thanks a lot for this comment. It solved my problem. I'm now using:
>
> \defineXMLenvironment
>   [appendices]
>   {%
>     \startappendices
>       \setuppagenumbering
>         [%
>           way=bytext,%
>           partnumber=no,%
>           conversion=numbers,%
>           location={header,right}%
>         ]%
>         \startstandardmakeup
>           [%
>             headerstate=empty,%
>             pagestate=start%
>           ]
>           \framed
>             [%
>               width=\textwidth,%
>               frame=off,%
>             ]
>             {%
>               \ss\switchtobodyfont[60pt]\setupinterlinespace[line=2.8ex]
>               Appendices
>               \writetolist[part]{Appendices}{}
>             }
>         \stopstandardmakeup
>   }
>   {\stopappendices}
>
> And it does exactly what I want.
>   

less messing around with %'s:

\defineXMLenvironment
  [appendices]
  {\directsetup{appendices:start}}
  {\directsetup{appendices:stop}}

\startsetups appendices:start
    \startappendices
        \setuppagenumbering [
            way=bytext,
            partnumber=no,
            conversion=numbers,
            location={header,right}
        ]
        \startstandardmakeup [
            headerstate=empty,
            pagestate=start
        ]
        \framed [
            width=\textwidth,
            frame=off
        ] {
            \switchtobodyfont[60pt,ss]
            \setupinterlinespace[line=2.8ex]
            Appendices
            \writetolist[part]{Appendices}{}
        }
        \stopstandardmakeup
\stopsetups

\startsetups appendices:start
    \stopappendices
\stopsetups

(spaces and lineending are ignored, use \space when a space is needed) 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2006-05-03 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 22:56 Johannes Graumann
2006-04-28  8:01 ` Willi Egger
2006-04-28 18:45 ` nico
2006-04-29 13:08 ` John R. Culleton
2006-05-01 17:02   ` Johannes Graumann
2006-05-03 19:57     ` Hans Hagen [this message]
2006-05-03 23:10       ` Johannes Graumann
2006-05-04  6:47         ` Hans Hagen
2006-05-04 16:16           ` Johannes Graumann

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=44590B24.4090303@wxs.nl \
    --to=pragma@wxs.nl \
    --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).