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.
From IDE menu goto Tools -> Options -> Editor -> Advance Options -> Default Charator Encoding only support in JavaSource only!!! so how to edit properties file in UTF-8 or in JSP
Created attachment 40083 [details] Properties file editor doesn't support charactor encoding UTF-8!!!
Hope we can have this feature. Thanks
I just find a walk through for this. In Tools -> Options -> Editor -> Advance Options -> IDE Setting -> System -> Object Type -> DTD Objects, add properties to the extensions and MIME Types. Then I can edit the UTF-8 encoding properties files . But I will lose the menu assigned to properties. I know there is a netbeans addon which add a menu to let open a file as other type. But I don't remember what's it's name.
nb6 has concept of project encoding property is this issue about jsp files or property files ? ken.frank@sun.com
nb6 has concept of project encoding property; the java property mentioned will not be present and wont be needed. is this issue about jsp files or property files ? ken.frank@sun.com
ksupakorn, windli: Can you please check the latest builds of 6.0? There is "Encoding" property of the project that is used for entire sources of it. Does that work for you? Thanks.
As of nb6.0 that is work for me. How can I close the issue?
Created attachment 46940 [details] a utf-8 file which still not works in netbeans
Created attachment 46941 [details] the expected look of autopager.properties
Hi ppis It's still not work for me. See the two new attached files. When I open the attached utf-8 file in netbeans, it will not show the content correctly. And after I modify it, it will be convert to \uxxxx format. I hope the utf-8 files can be opened and saved in utf-8 format also. Not convert the content to \uxxxx. Is this possible in the last build? Thanks Wind
Mariane, could you please have a look at it? Thanks.
Properties files are always loaded/saved using encoding ISO-8859-1, with non-ASCII characters decoded/encoded from/to \uxxxx sequences (where 'xxxx' is a sequence of four hexadecimal numbers). There is currently no way (from the user's point of view) to specify another encoding to be used. There is a request for enhancement named "Add support for other encodings (other than ISO-8859-1)" already filed - see issue #75906. I have also described the current mechanism of encoding/decoding in one comment of issue #75906 (comment filed on Apr 27 06:57:17 +0000 2007). Marked as a duplicate of issue #75906. *** This issue has been marked as a duplicate of 75906 ***