I would be useful to have a property editor for file encoding, which could be
reused by multiple modules. Currently Encoding can be specified for Java and
JSP files, but the UI is not user friendly, as the user must remember exact
spelling of the encoding. A drop down list containing all applicable encodings
would be more user-friendly.
Set target milestone to TBD
There is a GUI in the properties module which could be partially
copied, though it is not a property editor.
Changing to defect after consulation with nb QA and comments from nb
strategy that some i18n rfes could actually be viewed as defects.
Let me know if more details are needed.
Changing back to enhancement, the qa didn't specified it that way.
Passing this request to loaders. AFAIK there's no class that
encapsulates the concept of encoding - it's just a string. So there's
no way for the core to know to use an encoding editor instead.
Also, core/openide is no longer in the business of providing general
purpose property editors. Loaders defines the relationship between
documents and files, so that seems like an appropriate place to
I am pretty sure, that if special cooperation is needed, it can be
handled between java and JSP in their apis. But as this issue is old I
doubt the real need exists.