Migrate Netbeans Modules project that used native encoding from nb551 to nb6
All Chinese charactors display garbage, i will attach screenshot
Can't set Netbeans Modules project encoding, the default is UTF-8
If this is wrong catalog to file this issue, please modify to correct one.
Created attachment 54129 [details]
this project type does not have a project encoding property by design.
Developer will be able to comment on the migration situation as
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.
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
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.
*** Issue 134858 has been marked as a duplicate of this issue. ***