#96 [369] Unicode problems

open
closed-invalid
nobody
emitter (227)
6
2001-05-11
2000-11-14
Anonymous
No

[369]
From kzielinski@supermedia.pl Tue Nov 14 13:37:10 2000
Received: from localhost (IDENT:nobody@localhost [127.0.0.1])
by oss.software.ibm.com (8.9.3/8.9.3) with ESMTP id NAA11102
for <jikes-bugs@oss.software.ibm.com>; Tue, 14 Nov 2000 13:37:09 -0500
Date: Tue, 14 Nov 2000 13:37:09 -0500
From: kzielinski@supermedia.pl
Message-Id: <200011141837.NAA11102@oss.software.ibm.com>
To: jikes-bugs@oss.software.ibm.com
Subject: Lost encoding.

Full_Name: Krzysztof Zielinski
Version: jikes-1_12-mingw-win32.zip and jikes_1.10-6_i386.deb
OS: WinNT,Linux debian
Submission from: (NULL) (212.75.100.20)

I don't know if this is a bug, but JavaC (jdk1.2) work OK.

Jikes lost encoding after compiling.
(XML in encoding UTF8 to encoding ISO-8859-2)
A source
document.createTextNode("Witajcie, z pewnością macie mnóstwo
wrażeń i wspomnień ze swoich podróży.")

Compiled in javac [part compiled file]
Witajcie, z pewnością macie mnóstwo wrażeń i wspomnień ze
swoich podróży.

Compiled in Jikes
Witajcie, z pewnością macie mnóstwo
wrażeń i wspomnień ze swoich podróży.

Discussion

  • Chris Abbey
    Chris Abbey
    2001-05-11

    • status: open --> closed-invalid
     
  • Chris Abbey
    Chris Abbey
    2001-05-11

    I hope I understand what this bug report is saying, I may be miss-interpreting it though....
    The mingwin binaries do not have encoding support compiled in, so I dont' see how it could have been expected to deal with a .java file containing utf8 sequences. We don't provide .debs, so I don't know if whoever built it included any encoding support either. Assuming they did, and you used the proper "-encoding utf-8" switch we would require an actual compilable test case to action this defect. Closing it out as there is nothing we can do.