From: Tobias Burnus <burnus@gmx.de>
Subject: setupheadertexts + kap/uppercase
Date: Sat, 21 Jan 2006 17:15:57 +0100 [thread overview]
Message-ID: <43D25E3D.7020608@gmx.de> (raw)
Hello,
I think I have a expand problem.
I want to have
\setupheadertexts[pagenumber][{\getmarking[chapter][current]}][section][pagenumber]
with the chapter in \uppercase/\kaps. The problem is that
adding a \uppercase or \kap before the {\getmarking} ends up with
nothing and all my attemps with expand* ended up with either the same
result or with a TeX error message.
Using \setupheader[style=kap] (or =cap) does not work - as TeX bails out:
! Undefined control sequence.
\p!doifinstringelse ...ifinstringelse #2#1}@@\war
Any idea how to solve this?
Tobias
PS: I just saw that I asked the same question two years ago (15 January
2004):
http://www.mail-archive.com/ntg-context@ntg.nl/msg02175.html
next reply other threads:[~2006-01-21 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 16:15 Tobias Burnus [this message]
2006-01-21 17:12 ` Sebastian Rooks
2006-01-21 18:37 ` Tobias Burnus
2006-01-23 11:07 ` Hans Hagen
2006-01-23 15:06 ` Tobias Burnus
2006-01-23 15:54 ` Hans Hagen
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=43D25E3D.7020608@gmx.de \
--to=burnus@gmx.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).