db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-244) with linux, depending on env setting $LANG and console encoding, some i18n tests fail
Date Tue, 18 Jul 2006 14:49:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-244?page=comments#action_12421882 ] 
            
Myrna van Lunteren commented on DERBY-244:
------------------------------------------

Thx Knut, for testing with IBM jvm...

I have some tidbits of half-researched information that may/may not be related, this is just
a memory dump:
 - I noticed that when you're on Unix and $LANG is set to en_US.UTF-8, there is a difference
in what file.encoding gets set to. With sun's jvm file encoding remains ISO-8559-1, but IBM's
jvms pick up UTF-8. (I run a trusty little java program that just prints out all system properties).
 - As a result, I've been running our tests with ibm jvms with $LANG set to en_US. (which
is problematic on zOS, where $LANG appears to indicate a programming language, and en_US is
just not valid for $LANG.)
 - I think there actually may be an odd kind of bug in ij when the file.encoding is UTF-8.
I want to research that further.
- Note also that RunTest does try to do something with the console encoding in certain cases.

- I have been thinking that maybe if we can figure out why setting the encoding only really
works with sun jvm 1.5, we could maybe use derbyTesting.encoding for these tests. Andrew had
logged a bug 1027, but the actual problem may not be with the test harness, see Deepa's (Feb
7 2006)  comments in re DERBY-683.
- part of all this is also to include the i18n/LocalizedDisplay.sql and LocalizedConnectionAttributes.sql
tests into a suite at some point.
- I tried to make the test harness hide some of the problems by wrapping the non-ascii characters
in >Enc ### < lines. But I think that never worked properly.


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

        

Mime
View raw message