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.
Issue: When I delete the property in Properties file, some methods are exist. If I delete the entry which has Japanese name ... In one method, Property name is appeared in Japanese characters in confirmation dialog. In other method, Property name is appeared in Unicode in confirmation dialog. I feel sense of incongruity for this phenomenon. Environment: - S1S nevada Build This issue is not occurred in S1S trunk Build or Netbeans Dev Build. - probably all platforms I found this issue on Solaris 8, Win2000, and RedHat Linux 7.2. To Reproduce: 1. Create new properties file. 2. Add a new entry which has "Japanese key" and any value. 3. From Filesystems tab in Explorer Window, expand new properties file's node. 4. Right click "Japanese key" and select "Delete". Japanese key name is appeared correctly in confirmation dialog. (See also "Shot 1") 5. Click "No". 6. Right click properties file and select "Open". 7. Select entry which has "Japanese key" and click "Remove property" Button. Japanese key name is appeared in unicode source in confirmation dialog. (See also "Shot 2") Tip: - In "Step 7" of "To Reproduce", Japanese key name is appeared correctly in S1S trunk Build or Netbeans Dev Build.
add keyword "I18N".
Created attachment 9862 [details] Shot 1: Key name appears in Japanese character.
Created attachment 9863 [details] Shot 2: Key name appears in unicode source.
Reassigning to properties.
I am able to reproduce this issue..
more info:i am able to reproduce the issue on zh_CN locale. Locale:zh_CN Encoding:EUC
Fixed in trunk code as a side effect of issue 30664.
Hello Petr, I found that, this issue is re-appeared in followings. - S1S Nevada Build (030607_2) on sparc. First of all, this issue is not occurred in S1S trunk Build or NetBeans as my 1st report. Could you re-investigate this? Hiroshi
I took over ownership of the Properties module too late for being able to fix it in time for S1S 4.1. Since this issue is solved in current development builds of NetBeans, I mark it as fixed.
Fix was verified this issue on nb36(040218), sparc.