Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2841246.1155581054936.JavaMail.jira@brutus>
Date: Mon, 14 Aug 2006 11:44:14 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-244) with linux, depending on env setting
 $LANG and console encoding, some i18n tests fail
In-Reply-To: <1075012607.1114715323467.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-244?page=all ]

Knut Anders Hatlen updated DERBY-244:
-------------------------------------

    Attachment: 244-3.diff

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
in RunTest.java:

  - adds a new variable, codeset, which holds the value of
    derby.ui.codeset if it is specified by the test in
    XXX_app.properties

  - 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.

> with linux, depending on env setting $LANG and console encoding, some i18n tests fail
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-244
>                 URL: http://issues.apache.org/jira/browse/DERBY-244
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.1.1.0
>         Environment: Linux, with console.encoding *not* UTF-8
>            Reporter: Myrna van Lunteren
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: 244-2.diff, 244-2.stat, 244-3.diff, 244.diff, 244.stat
>
>
> The tests
>    i18n/messageLocale.sql
>    i18n/urlLocale.sql
>    i18n/iepnegativetests_ES.sql
> will fail on Linux if $LANG and as a result, console.encoding is not set in the same way as when the test master was created. The behavior is that some characters are not seen as outside the ANSI range and are displayed as a ?.
> Result is as master when $LANG is en_US.UTF-8
> But then ieptest.sql will fail which will with ibm142 which pass if $LANG is en_US.
> This needs some further analysis, so this description may need to be updated later.
> Whatever the solution is, will need to work for all situations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira