From: Tobias Burnus <burnus@gmx.de>
Subject: Re: setupheadertexts + kap/uppercase
Date: Sat, 21 Jan 2006 19:37:43 +0100 [thread overview]
Message-ID: <43D27F77.7070809@gmx.de> (raw)
In-Reply-To: <43D26B6A.9060509@free.fr>
Hello,
Sebastian Rooks schrieb:
> Did you try with a \fetchmark[chapter][first] as explained on the wiki ?
> http://wiki.contextgarden.net/Headers_and_Footers , section 2 "Using
> capitals"
That indeed worked. (I looked at ConTeXtgarden, but I seemingly missed
the right keyword in my search :-( shame on me.)
Anyway, \uppercase have some problems. I get with
---------------------------
\enableregime[utf]
\setupheadertexts[][{\expanded{\uppercase{\fetchmark[chapter][first]}}}]
\starttext
\chapter{Einführung} % EINFÜHRUNG
\uppercase{ÄÖÜäöüß} % should be ÄÖÜÄÖÜSS
\stoptext
---------------------------
"ÄÖÜÄÖüß" ("üß" should be "ÜSS") and in the header I get "EINFßHRUNG".
Tobias
next prev parent reply other threads:[~2006-01-21 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 16:15 Tobias Burnus
2006-01-21 17:12 ` Sebastian Rooks
2006-01-21 18:37 ` Tobias Burnus [this message]
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=43D27F77.7070809@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).