You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2008/11/21 19:55:44 UTC
[jira] Commented: (DERBY-1726) Make i18n/LocalizedDisplay.sql and
i18n/LocalizedConnectionAttribute.sql behave equally on different platforms
[ https://issues.apache.org/jira/browse/DERBY-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649749#action_12649749 ]
Myrna van Lunteren commented on DERBY-1726:
-------------------------------------------
I'll comment a little - shooting from the hip - and experiment later.
One reason I haven't worked more on this is that I no longer have access to a Japanese machine so it's hard to get anything with that encoding going anymore.
Re 3 in Knut's comment of Aug 19 - I think the ? are ok, they represent the result of the output run through an english console.encoding, and/or file.encoding, which I don't think we can change...I believe any time a character not recognized in the current encoding (or is it codeset? or codepage?) need to be printed it gets a ?. So even if we managed to get this through Japanese encoding, I think we'd still see ? in the output. If someone knows better than me on this, please correct me!
Re using constructor with encoding parameter - I think indeed, we should have a different encoding. As Kathey said and Knut noticed, currently the test really runs in US-ASCII...Maybe that's ok for this test, which judging by the name was really intended to test LocalizedDisplay.
Other tests that test derby.ui.codeset is LocalizedConnectionAttribute.sql/LocalizedAttributeScriptTest, which I think has the same issue as LocalizedDisplay...and is ISO-8559-1, which is not different enough from US-ASCII, I think, to be a problem or make a difference...
And tools/SysinfoLocaleTest.java.
So not a whole lot, and no other ij tests...
> Make i18n/LocalizedDisplay.sql and i18n/LocalizedConnectionAttribute.sql behave equally on different platforms
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1726
> URL: https://issues.apache.org/jira/browse/DERBY-1726
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: DERBY-1726_1.diff, DERBY-1726_2.diff, DERBY-1726_3.diff, DERBY-1726_3.stat, DERBY-1726_4.diff, DERBY-1726_5.diff, DERBY-1726_6.diff, DERBY-1726_7.diff, DERBY-1726_7.stat, DERBY-1726_8.diff, props.java
>
>
> Myrna van Lunteren commented on DERBY-244:
> The one remark I have is that I still cannot get the LocalizedDisplay.sql and LocalizedConnectionAttribute.sql test from the i18n directory to behave the same under windows and Linux (with sun jdk 1.4.2.).
> For windows, I had to update the masters for these tests, but running them on Linux still failed for me.
> With jdk131, ibm131 and ibm142 the LocalizedDisplay.sql test hung, and LocalizedConnectionAttribute exits with a MalformedInputException.
> It would be nice if we could figure out a way to add these tests to the suites...
> --- stack of LocalizedConnectionAttribute on Linux ---
> Exception in thread "main" sun.io.MalformedInputException
> at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java(Compiled Code))
> at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
> at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
> at java.io.InputStreamReader.read(InputStreamReader.java:208)
> at java.io.BufferedReader.fill(BufferedReader.java:153)
> at java.io.BufferedReader.readLine(BufferedReader.java:316)
> at java.io.BufferedReader.readLine(BufferedReader.java:379)
> at org.apache.derbyTesting.functionTests.harness.RunTest.setDirectories(RunTest.java:729)
> at org.apache.derbyTesting.functionTests.harness.RunTest.main(RunTest.java:262)
> ----------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.