Bug 20259 - I18N -There is not a standard property editor for Encoding
I18N -There is not a standard property editor for Encoding
Status: RESOLVED WONTFIX
Product: platform
Classification: Unclassified
Component: Data Systems
3.x
All All
: P2 (vote)
: 6.x
Assigned To: Jaroslav Tulach
issues@platform
: I18N
Depends on:
Blocks: 19928
  Show dependency treegraph
 
Reported: 2002-02-07 14:18 UTC by Petr Jiricka
Modified: 2008-12-22 18:45 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2002-02-07 14:18:23 UTC
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.
Comment 1 Marek Grummich 2002-07-22 11:49:44 UTC
Set target milestone to TBD
Comment 2 Marek Grummich 2002-07-22 11:53:13 UTC
Set target milestone to TBD
Comment 3 Jesse Glick 2002-08-27 16:06:48 UTC
There is a GUI in the properties module which could be partially
copied, though it is not a property editor.
Comment 4 Ken Frank 2002-10-12 18:59:59 UTC
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.
ken.frank@sun.com
Comment 5 Peter Zavadsky 2002-11-12 16:31:02 UTC
Changing back to enhancement, the qa didn't specified it that way.
Comment 6 _ tboudreau 2003-11-20 16:52:24 UTC
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
implement this.
Comment 7 Jaroslav Tulach 2005-02-11 12:51:18 UTC
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.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo