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.
| Summary: | I18N - Can't set project encoding for some NB projects | ||
|---|---|---|---|
| Product: | apisupport | Reporter: | Will Zhang <wzhang> |
| Component: | Project | Assignee: | Martin Kozeny <mkozeny> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | jf4jbug, kfrank, liujiaguang |
| Priority: | P3 | Keywords: | I18N |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Attachments: | screenshot | ||
|
Description
Will Zhang
2007-12-11 08:46:15 UTC
Created attachment 54129 [details]
screenshot
this project type does not have a project encoding property by design. Developer will be able to comment on the migration situation as described here. ken.frank@sun.com Encoding setting only exists in some standard projects, e.g, java project, but all nb projects. Some Chinese users hope to add encoding setting into all nb projects. moving back to p3 since it is as designed. Its not done yet that all project/file encoding additional functionality and enhancements has been completed and that was the scope of it for nb6,but the large functionality related to it already has been a big step to meet user requests for this functionality so far is now in nb6. Thanks for mentioning about this Will as it should be clarified more. to provide this communication I will: add this info above to some other issues. change this one to apisupport, which is the category; then developer there can see if this is a situation that should have the project encoding property also, and then it could be raised back to p2 if they agree. add information about a module that allows users to open files and save files in a particular encoding that might allow a workaround for some of these parts not yet fully implemented. this is actually duplicate of an older issue but I need to find which one it was. ken.frank@sun.com Correct, NBM projects currently only support UTF-8 encoding. If someone can't migrate his project from nb5.5 to nb6.0, or he can't find his favorite menuitems in the new version ide, perhaps he will regard this as a degeneration and feel lost :-( By contrast with Eclipse and JBuilder, nb fans expect adding more features to NetBeans. for example，import or export java code format options, set encoding to any file optionally, provide javadoc/javabean editor. Chinese: 如果某人不能把他的项目从nb5.5移植到nb6.0，或者他不能在新版本IDE中找到他喜欢用的菜单项，他就多半会把这看作是一种退化并感 到失落 :-( 与Eclipse和JBuilder相比较，NB的爱好者期盼在NetBeans里加入更多特性， 比如导入/导出Java格式设置、每个文件都可设定字符集、提供javadoc/javabean编辑器等。 NB 5.5 didn't support specific project encodings at all, so a project using non-ASCII characters could not be trusted to open on another machine; this is fixed in NB 6. For a migration to UTF-8 you can use e.g. the native2ascii and ascii2native tools in the JDK. Support for alternate encodings in NBM projects will be considered for a future release. changing back to feature as per Jesse's comments; Jesse if it should be RFE instead or stay as defect please let me know. ken.frank@sun.com *** Issue 134858 has been marked as a duplicate of this issue. *** |