[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: serious flaw of @c
From: |
Karl Berry |
Subject: |
Re: serious flaw of @c |
Date: |
Fri, 21 Nov 2008 18:28:03 -0600 |
And since comment removal works before macro expansion
That's my belief too. I'm pretty sure there is no way,
unfortunately.
In my CJK package, I use character code 0x7F for various purposes
since this is not used anywhere else, in no encoding.
I didn't know that. Cool! Not even as a second/subsequent byte in
multibyte encodings?
The other problem is how to specify it. I mean, sure, we can add the
\catcode, and then it will work literally, but that will render the
source file non-ASCII, which is a drag.
We could make ^^? work, since ^ is active anyway, but that's going to
turn into macro expansion again and presumably will have all the same
issues as @c does now. Hmm.
or a complete new way of designing macros?
This.
One goal I was thinking of was to make it possible to simply use \def in
the texinfo.tex implementation. At least that would be robust. But
newline handling just defeats me, as I said ...
thanks,
k