Description of problem:
The default encoding for everything in eclipse is UTF-8. When IBM or
BEA jvm tries to open a file marked UTF-8 with non-UTF-8 characters
(image files, libraries, foreign characters) it fails. This is
expected behavior from the jvm. However as all files have this
setting the jvm runs into many problems building and constant problems
searching. Eclipse.org does not share this problem the only reason I
can think for this is they either build it with sun jvm or change LANG
Steps to Reproduce:
1. Try to build something with foreign characters in a source file or
perform a search on image files
*** Bug 139521 has been marked as a duplicate of this bug. ***
*** Bug 141794 has been marked as a duplicate of this bug. ***
Turns out this happens only with IBM jvm (BEA is not affected) and
eclipse.org IS affected, as to the confusion see bug 141831.
The problem can be worked around by changing LANG to "ISO-8859-1"
before starting up eclipse, unfortunatly this also leads to the output
on the command line of,
(process:12516): Gdk-WARNING **: locale not supported by C library
(process:12516): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
still this is far less problematic than the problems encountered.
Tracking upstream bug
The major manifestation of this, searching problems, have been fixed
by a recent backport, the inability to open certain files while an
annoyance is a problem with the files themselves, not with the jvm or
eclipse itself. Closing the bug although we should still find some
way to get support for non text files which is a current and
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.