ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Subject: headertext + cap/uppercased problem
Date: Thu, 15 Jan 2004 16:51:36 +0100	[thread overview]
Message-ID: <20040115155136.GA30268@physik.fu-berlin.de> (raw)

Hello,

(partially this is a resent.)

I have a problem forcing captial letters for the header(texts).
I tried
(a) \kap in \setupheadertexts, but then \getmarking gets not expanded
    (I only get 'CHAPTER :' which looks rather strange)
(b) Using \uppercased in \setupheadertext produces an error

(c) Using \setupheader[style=kap] or style=\uppercased produces errors

Tobias

 * * *

I use
\setupheadertexts
            [][{\it\getmarking[sectionnumber]~~~\getmarking[section]}]
            [{\it Chapter \getmarking[chapternumber]: \getmarking[chapter]}][]

which works well. Adding  \setupheader[style=cap] (or style=\uppercased)
I get the following  error. Any idea why?

Tobias

! Missing } inserted.
<inserted text> 
                }
<to be read again> 
                   \vskip 
\doplacelayouttextline ...\scratchpagebox }\vskip 
                                                  -#2\relax \fi 
\gettextboxes ...eropoint \the \headertextcontent 
                                                  \vskip \hoofdhoogte
\fi \v...

\@@lymethodenormal ...interlineskip \gettextboxes 
                                                  \dostopattributes
\egroup ...

\buildpagebody ...?ly \c!methode \v!normaal }}#1#2
                                                  \ifcase
\pageornamentstate...
...
l.78 \page[right]

             reply	other threads:[~2004-01-15 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 15:51 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14  9:44 Tobias Burnus

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=20040115155136.GA30268@physik.fu-berlin.de \
    --to=tobias.burnus@physik.fu-berlin.de \
    --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).