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 - File Encoding options | ||
---|---|---|---|
Product: | java | Reporter: | nguyenq <nguyenq> |
Component: | Source | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jf4jbug, kfrank, mgrummich |
Priority: | P3 | Keywords: | I18N |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
nguyenq
2003-03-28 22:18:36 UTC
Agreed. This week I will commit an enhancement to the Integer/int property editors which will allow key/value pairs to be supplied. This would be a good usage of it. See issue 20736 for details. I do not know off the top of my head who provides the Encoding property (and I know it is used differently in the new Projects branch, in at least one dialog, so it will need to be handled for both cases). Maybe the Java module? As Encoding is a string value, there's nothing that can be done directly in core/property editors to handle this case - the code that is providing the property needs to either provide a custom property editor or provide appropriate hints to the existing property editor - or create some "Encoding" class so a specific property editor may be assigned. Assigning back to issues@core for appropriate resolution. assigning to owner of subcomponent Passing property editor issues to new owner, Jirka As of today, this issue still has not been resolved. core->java *** Issue 51670 has been marked as a duplicate of this issue. *** *** Issue 62754 has been marked as a duplicate of this issue. *** I think this is a dup of bug 42638. Let's cleanup these encoding issues. Tomas is file encoding guru :) The encoding model has dramatically changed in NB 6.0, this issue is no more valid. |