🚀 go-pugleaf

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

>I think I'm using the latest of everything:

You are more up-to-date than I am.

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


That explains it.  The extended characters are made active (like ~) and
behave just like \control \sequences.  As is the case for the \ae command, 
an active f is not affected by \uppercase.  This method of mapping input 
characters prohibits command names like \Cfsar. 

If the character mapping for the keyboard matches the mapping in the fonts,
then the set-up should be

 \catcode198=11
 \catcode230=11

 \uccode`f=`F \lccode`f=`f
 \uccode`F=`F \lccode`F=`f

Unfortunately, if the mappings of the input and output character sets are
not the same, they can only be adjusted as part of the instalation of TeX!

If your TeX does not have a useful input mapping, and supposing that  
it is impractical to compile TeX with the correct input
character translation table, you will be stuck using active characters 
for any characters that don't match.

Doesn't it seem like a Bad Idea to have the character translation so 
hard to change?  Especially since nobody can agree on character encoding
except for SOME (about 90) of the ascii codes ("20-"5A, "61-"7E).


Donald