PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3047
*** shadow/3047 Thu Aug 9 06:41:08 2001
--- shadow/3047.tmp.18565 Thu Aug 9 09:35:27 2001
***************
*** 73,75 ****
--- 73,90 ----
Joe specified.". Are you implying that with the latest CVS code I should see
the two bytes 195 and 188 as the output in my example, instead of the � which I
currently get with Version 2.1.0?
+
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-08-09 09:35 -------
+ >Are you implying that with the latest CVS code I should see
+ >the two bytes 195 and 188 as the output in my example, instead of the � which
+ I
+ >currently get with Version 2.1.0?
+
+ I think you may see the same thing with 2.1.0 as with the latest CVS code,
+ though I'm not absolutely sure about this. I think 195 and 188 may be viewed
+ as � in some editors, which is the correct display mode. For instance, if I
+ open a xml file with 0xC3 0xBC in XMetal, it correctly displays it as �.
+
+ To be sure what your output is with 2.1.0, you should look at the output file
+ with a hex editor or some such thing.
\ No newline at end of file
