From: Berend de Boer <berend@pobox.com>
Subject: Unexpected side effects when using \cap in custom headings
Date: Tue, 14 Nov 2000 13:19:01 +0100 [thread overview]
Message-ID: <3A112DB5.468A25DE@pobox.com> (raw)
Hello All,
I think I've found a bug. If you use \cap in a custom heading, the
reference is also capitalized. As you will see the reference [sec:test]
will not be found.
------------------------
% interface=en
\setupbodyfont
[ber,pos,ss]
% capitalize headings
\def\myhead#1#2%
{\cap{#2}}
\setuphead
[chapter]
[command=\myhead]
\starttext
\chapter[sec:test]{Test}
\input tufte.tex
See \in{chapter}[sec:test] or \in{chapter}[SEC:TEST].
\stoptext
------------------------
I think I'm using the latest beta (oct 3).
Groetjes,
Berend. (-:
next reply other threads:[~2000-11-14 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 12:19 Berend de Boer [this message]
2000-11-14 13:50 ` Hans Hagen
2000-11-14 15:05 ` Berend de Boer
2000-11-14 15:51 ` 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=3A112DB5.468A25DE@pobox.com \
--to=berend@pobox.com \
/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).