From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3321 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Unexpected side effects when using \cap in custom headings Date: Tue, 14 Nov 2000 14:50:43 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20001114145043.013f0780@pop.wxs.nl> References: <3A112DB5.468A25DE@pobox.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: main.gmane.org 1035394061 16030 80.91.224.250 (23 Oct 2002 17:27:41 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:27:41 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Berend de Boer In-Reply-To: <3A112DB5.468A25DE@pobox.com> Xref: main.gmane.org gmane.comp.tex.context:3321 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3321 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 -------------------------------------------------------------------------