On Tue, May 13, 2003 at 02:38:24PM -0700, White, John K wrote:
> i wonder if this is related to JavaCC's ASCII_UCodeESC_CharStream class that is generated to handle
> token input for the parser? perhaps it can't handle double-byte characters. or, as the class name
> suggests, do unicode character sequences need to be escaped in some way? the latest CVS version
> uses JavaCC 3.0, which generates a different CharStream implementation class... maybe it's magically
> fixed in CVS? i'm not too familiar with locale issues in java. hopefully someone else knows more...
When I saw this message I tried pasting the test of the email into BeanShell
in my xterm... and it printed what I saw in the email... which means nothing
I guess. I will try it when I get home on a terminal that supports more
I must confess that I don't fully understand or know how to debug the
I18N issues because I don't really know what people mean when they say that
it isn't working... I think we can enter unicode escaped text ok. I assume
the problem is in entering straight unicode bytes in a stream... I guess
I could put some bytes into a file and read them and print them with bsh...
If someone can educate me or tell me what's broken I'll be happy to fix it.