This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
to reproduce: 1. From Source Editor, right click for any web.xml file (e.g. web.xml in "CD Shop Cart" which is bundled tutorial in FFJ), and select [Property]. 2. Open for any property which has Description field (e.g. [Resource Reference] property in [References] tab) , input for any name (which contains ascii characters) and input Description which contains japanese characters. 3. Click [OK] twice. 4. Right click edited web.xml file and select [open]. web.xml file is truncated.
Created attachment 4522 [details] Content of truncated file is same as screen shot.
Created attachment 4523 [details] Here is truncated xml file.
Additional reports: - When JDK 1.3.1 is used. Input Japanese characters from property editor ... web.xml file is truncated. Input Japanese characters from source editor ... Japanese characters are stored to web.xml file in UTF-8 encoding correctly. - When JDK 1.4 RC is used. Input Japanese characters from property editor ... web.xml file is not truncated. But, japanese characters are stored to web.xml file not correctly (with invalid encoding). Input Japanese characters from source editor ... Japanese characters are stored to web.xml file in UTF-8 encoding correctly.
Additional reports (on FFJ-EE, v.3.0, Build 020204): In latest build, Japanese characters are stored correctly. Details are following ... - When JDK 1.3.1 is used. Input Japanese characters from property editor ... <changed from last issue> web.xml file is not truncated. Japanese characters are stored to web.xml file in UTF-8 encoding correctly. Input Japanese characters from source editor ... Japanese characters are stored to web.xml file in UTF-8 encoding correctly. - When JDK 1.4 RC is used. Input Japanese characters from property editor ... <changed from last issue> web.xml file is not truncated. Japanese characters are stored to web.xml file in UTF-8 encoding correctly. Input Japanese characters from source editor ... Japanese characters are stored to web.xml file in UTF-8 encoding correctly.
Changing target milestone to FFJ 4.0
This issue is no longer re-appeared in current version.
Consistent use of the I18N keyword.