Unexpected side effects when using \cap in custom headings

Unexpected side effects when using \cap in custom headings

[Berend de Boer]

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. (-:

Re: Unexpected side effects when using \cap in custom headings

[Hans Hagen]

At 01:19 PM 11/14/00 +0100, Berend de Boer wrote:
>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.

Here it even blows -) 

The problem is that #2 is more than just the text, it's a bunch of terrible
things. [try \showargument{#2}]

Seems like you need a hook to the text. 

Conversion to uppercase is very tricky in tex, since there is more that
a->A [think of acccents] and expansion will definitely get in the way.
Either use an allcaps font or \sc. I suppose that setting up a virtual all
caps font is the best way out. 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: Unexpected side effects when using \cap in custom headings

[Berend de Boer]

Hans Hagen wrote:

> The problem is that #2 is more than just the text, it's a bunch of terrible
> things. [try \showargument{#2}]

Yep, can't you filter that out? It would be easiest of #2 contained only
the text without any styles/colors and whatsoever.

> Seems like you need a hook to the text.

I first thought that the textcommand option might be the one. But it
doesn't like command being defined or so.

Groetjes,

Berend. (-:

Re: Unexpected side effects when using \cap in custom headings

[Hans Hagen]

At 04:05 PM 11/14/00 +0100, Berend de Boer wrote:
>Hans Hagen wrote:
>
>> The problem is that #2 is more than just the text, it's a bunch of terrible
>> things. [try \showargument{#2}]
>
>Yep, can't you filter that out? It would be easiest of #2 contained only
>the text without any styles/colors and whatsoever.

Nop. Since you want the fonts etc to be part of it as well as in pointer
sensitive viewers the ref at that place. 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------