db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-244) with linux, depending on env setting $LANG and console encoding, some i18n tests fail
Date Thu, 27 Jul 2006 07:59:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-244?page=all ]

Knut Anders Hatlen updated DERBY-244:

    Attachment: 244-2.diff

Attaching new patch (244-2.diff). The only change from the previous patch is that it uses
-Dconsole.encoding=UTF-8 instead of -Dconsole.encoding=Cp1252 for the i18n tests.

Derbyall runs cleanly with the patch on Sun JVM 1.5.0. There were a couple of failures on
IBM JVM 1.5.0 (ran with LC_ALL and LANG set to ja_JP.eucjp), but they were already logged
in JIRA. I have also run the i18nTest suite successfully on IBM JVM 1.4.2.

Reviews would be welcome! Thanks.

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


View raw message