On Thu, Nov 09, 2006 at 05:46:12PM +0100, Georg Baum wrote: > Am Donnerstag, 9. November 2006 14:15 schrieb Enrico Forestieri: > > On Thu, Nov 09, 2006 at 01:26:31PM +0100, Georg Baum wrote: > > > > > We have unicode for document contents. We don't have unciode for > internal > > > keywords. This is the same as in LaTeX: You cannot define commands with > > > non-ascii characters. > > > > You know you are wrong here, don't you? ;-) > > No, i mean that seriously. cat code games are dirty TeX hacks. \newcommand > does not work with nonascii command names.
I don't know what you mean, perhaps that they don't work if you don't catcode them when using the standard latex format? But I could easily create a latex.fmt in which all of them are letters, so I would not need to explicitly use \catcode. It is plain dumb that I cannot use non-ascii chars in defining commands, or layouts. I remember when the Mac had no colours and everyone using it was argumenting that colour is not important... -- Enrico
catcode.tex
Description: TeX document
