Message1274

I only see one problem in these changes: calling String.getBytes with ISO-8859-1 uses CodingErrorAction.REPLACE in its internal CharsetEncoder.  That just replaces characters above 255 with '?'.  I think we want it to throw an exception, right?

Unfortunately, CharsetEncoder appeared in Java 1.4 so we can't just use it directly for 2.2. As far as I can tell, there's no way in versions earlier than 1.4 to get that kind of control over the encoding in Java's library.  We may have to write a bit of code in PyString or the like that handles converting Strings to bytes and reports errors instead of eating them.  This applies to http://jython.org/bugs/1599900 as well.