Hi, On Sat, 2004-03-27 at 15:23, Jeroen Frijters wrote: > Currently, if you System.out.println() a string containing an > unencodeable character, the line gets silently swallowed, instead the > unencodeable character should be replaced by a question mark (at least > that's what Sun does on Windows). > > This behavior doesn't appear to be specified anywhere, but testing > suggests that the proper way to do this is by calling setBadCharValue on > the Encoder in OutputStreamWriter. > > OK to apply?
This looks fine to me. The new java.nio.charset.CharsetEncoder also seems to contain this functionality so it should be easy to switch to that (when someone has time to rewrite our current EncodingManger approach to it). Cheers, Mark
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
