NetBeans IDE Dev (Build 200604101800)
1.5.0_06; Java HotSpot(TM) Client VM 1.5.0_06-b05
Windows XP version 5.1 running on x86
cs_CZ (nb); Cp1250
I used (for previous builds) pseudolokalized nb5.5 on windows
with jappanise locales for testing purposes, currently i switched
to trunk dev version and turned back to my czech locales.
i've opened project changed under localized nb and
have troubles with multibyte characters in editor and output
when i try to clean/build this project it fails
SEVERE [null]: getCanonicalFile() on file
java.io.IOException: The system cannot find the file specified
but my system itself have no problems reading multibyte characters,
even in project view i can see file name properly and even in editor
i can copy paste new multibyte characters.
only interpretation of characters comming from java file system is wierd.
Created attachment 29747 [details]
The described problems are mostly caused by the fact that the source code editor
and the compiler do not know which encoding to use for displaying and compiling
the file. Most probably both the editor and the compiler use the default
encoding for the current locale. If the encoding it specified for Java source
files (in the Options dialog), the files are displayed correctly. The same is
probably true for the compiler - it must be set in the project's properties.
It may also happen that the multibyte characters are not properly rendered in
the IDE - this is a matter of the JDK whether it uses the appropriate fonts.
None of these issues can be fixed or otherwise influenced by the I18n module -
reassigned to (pseudo-)module IDE for further dispatch.
if the encoding for the java files is changed to the ja or utf8 one
when you are in cz locale,
does it work or still problems
in showing the ja characters created when in ja locale.
I realize that the ide does not have any universal kind of encoding
detection, but wondering, if utf8 used when in ja locale, then make
sure its used when in cz locale, does it help.
for the compiler, however, is there an option for that just like there is for
#42638 necessary for fixing this sort of problems
*** This issue has been marked as a duplicate of 42638 ***