Thanks for the reviews, Myrna and Rick!
I also see that the tests fail with Sun JVM 1.4.2 under Linux when
LANG=en_US.ISO-8859-1. I don't know why, but it seems to work when
derby.ui.codeset is UTF-8.
I am uploading a new patch (244-3.diff) which has these extra changes
- adds a new variable, codeset, which holds the value of
derby.ui.codeset if it is specified by the test in
- sets derby.ui.codeset to UTF-8 in i18n tests for which no codeset
has been specified
- uses the encoding specified by derby.ui.codeset to read the output
from the test (but it is still written as UTF-8 to the tmp file)
This seems to fix all the tests in the i18nTest suite for all (LANG,
VENDOR, VERSION) in (en_US.ISO-8859-1, en_US.UTF-8) x (Sun, IBM) x
(1.4.2, 1.5.0) under Linux.
It is also possible that this patch makes LocalizedDisplay.sql have
the same behaviour on Windows and Linux, but I don't have any machine
running Windows to test it on. (I never saw the hang, by the way.)
LocalizedConnectionAttribute.sql fails because RunTest expects all sql
files to be UTF-8 encoded, while LocalizedConnectionAttribute.sql is
Cp850 encoded. I think this can be solved by using
InputStream/OutputStream instead of Reader/Writer to copy the sql file
from derbyTesting.jar to the test directory, but I won't add that to
this patch as it is messy enough as it is.