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.
Profiler 5.0, Japanese localizing version for 5.0 localized release Japanese environment in all platforms (I've not tested in Chinese environment, but I guess same problem is caused). to reproduce: - Run IDE in Japanese environment latest internal ML build should be used - Run Attach Wizard to attach Profiler to Sun App. Server 8.1 PE server location: Local attach method: Direct Integration Type: Automatic App. Server can not run after wizard because of XML error in domain.xml. [Fatal Error] domain.xml:2:5: Invalid byte 1 of 1-byte UTF-8 sequence. SUNWappserver/domains/domain1/config/domain.xml is modified by wizard. The inserted <profiler> entry is OK, but inserted comments at the top have problem: <!--This file was modified to allow integration with NetBeans Profiler--> <!--Backup of original version of this file should be located in the same directory with .backup extension--> In Japanese environment, the translated comments are inserted, but it's inserted as system default encoding (e.g. EUC-JP in Solaris, Shift_JIS in Windows). However, domain.xml should contain UTF-8 character. As a result, XML parsing error is caused. The translated comments should be inserted as UTF-8 character. Please note that same comments are inserted into SUNWappserver/config/asenv.conf This should be inserted as system default encoding, so the current implementation should be kept for asenv.conf. Workaround for internal ML build user: After Attach Wizard, edit domain.xml to remove translated comments. asenv.conf does not have to be modified manually. Workaround for 5.0 localization release: Back translate following messages into English: profiler-common/src/org/netbeans/profiler/common/integration/Bundle_ja.properties IntegrationUtils_ModifiedForProfilerString IntegrationUtils_OriginalBackupLocationString
Add I18N keyword.
Thanks for the bugreport. I've reproduced it in Chinese env, same problem occurs. The cause is that domain.xml is incorrectly saved in current (default) encoding, not in UTF-8 which is required for the file.
Affected bundle items marked as not to be localized in release50 branch. Format for domain.xml saving fixed to UTF-8 in trunk, added note to bundle items that strings are inserted into modified files. It's on l10n team decision - maybe these shouldn't be localized at all. But, if localized, they shouldn't break anything in the future. Fixed in trunk.
Fixed for 5.5.
assume fixed since no further reports in 55 release.