I think I will just go with moving the thing to Tomcat; it looks
like that's going to be easier than rewriting the mapping process in
Tcl.
Thanks for the input, everyone!
janine
On Sep 5, 2007, at 6:42 PM, Tom Jackson wrote:
On Wednesday 05 September 2007 17:53, Dave Bauer wrote:
Might work, might not. You could write a few tests by comparing
output
from tjhe Java to your new maintainable map. This assumes there is a
one-to-one mapping. I have no idea, I am not familiar with Chinese.
There are several steps, but processing is char-by-char. You have
to know how
to read a char. With UTF-16, this is easy. UTF-8 is harder to read.
Once you
have a char, you need a method to map it to the new character set.
Handling
errors is another story.
Also, if you are reading a channel, you can fconfigure as binary.
If you don't
do this, then Tcl will probably convert it to UTF-8. Use your char
reader on
a binary channel unless Tcl can do the conversion all by itself.
Don't expect too much, I have yet to find a browser which reads
UTF-8 100%
correct.
see: http://rmadilo.com/files/utf-8/UTF-8-test.txt
tom jackson
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
