🚀 go-pugleaf

>>>>> On 5 Aug 92 13:57:00 GMT, asnd@msr.triumf.ca (Donald Arseneau) said:

Donald> In article <ROLFL.92Aug5130152@karl.uio.no>, rolfl@karl.uio.no (Rolf Lindgren) writes...

[...]

>\catcode198=13	\chardefF="5D
>\catcode230=13	\chardeff="1A
> 
>\uccodef=F\lccodef=f
>\uccodeF=F\lccodeF=f


Donald> That explains it.  The extended characters are made active (like ~) and
Donald> behave just like \control \sequences.  As is the case for the \ae command, 
Donald> an active f is not affected by \uppercase.

[Note: the `ae' letter has been converted to an `f' somewhere on the net.]

This is not true.  `\uppercase' will act on any character with an
appropriate `\uccode'.  Take for eaxample the following TeX code:

	\uccode`\{=`a
	\uccode`\}=`b
	\uccode`\$=`c
	\uccode`\&=`d
	\uccode`\#=`e
	\uccode`\^=`f
	\uccode`\_=`g
	\uccode`\ =`h
	\uccode`\?=`i
	\uccode`\~=`j
	\uppercase{$^{}_{}$ ?~&#}}

Running this code through TeX will produce the following:

	This is TeX, C Version 3.141
	(utest.tex
	! Undefined control sequence.
	<to be read again> cfabgabchij
	                              dee
	l.11 \uppercase{$^{}_{}$ ?~&#}
	                              }
	? 

Now TeX complains about an undefined control sequence, namely the
active character `j'!

This little test clearly shows that active characters can be used to
input special letters and still have \uppercase work!

---
Frank Jensen,   fj@iesd.auc.dk
Department of Mathematics and Computer Science
Aalborg University
DENMARK