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.

Bug 32482 - I18N - File Encoding options
Summary: I18N - File Encoding options
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: Tomas Zezula
URL:
Keywords: I18N
: 51670 62754 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-28 22:18 UTC by nguyenq
Modified: 2007-09-20 11:49 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description nguyenq 2003-03-28 22:18:36 UTC 
Currently, the Text tab in a file's Properties window has 
a blank text field for Encoding property. It is desireable 
to replace this text field with a combo box populated with 
all, or most commonly used (ISO-8859-1, UTF8, etc.), the 
file encoding options supported by Java, for it could be 
daunting or error-prone for users to manually enter the 
encodings -- typo errors can happen and result in 
incorrect file saving. (Does the IDE currently have a 
mechanism to detect invalid values entered for Encoding?)

Possible values for the combo box can be found at 
http://java.sun.com/j2se/1.4/docs/guide/intl/encoding.doc.h
tml. At least, the Basic Encoding Set, in particular, 
should be used for the combo box.
Comment 1 _ tboudreau 2003-03-31 14:43:59 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.
Comment 2 Marian Mirilovic 2003-11-25 13:11:17 UTC 
assigning to owner of subcomponent
Comment 3 _ tboudreau 2004-04-19 14:53:12 UTC 
Passing property editor issues to new owner, Jirka
Comment 4 nguyenq 2004-11-26 01:35:43 UTC 
As of today, this issue still has not been resolved.
Comment 5 Martin Matula 2004-11-26 19:56:02 UTC 
core->java
Comment 6 Martin Matula 2004-11-26 19:56:40 UTC 
*** Issue 51670 has been marked as a duplicate of this issue. ***
Comment 7 Jan Becicka 2005-10-12 15:06:28 UTC 
*** Issue 62754 has been marked as a duplicate of this issue. ***
Comment 8 Masaki Katakai 2006-07-28 06:42:56 UTC 
I think this is a dup of bug 42638. Let's cleanup these encoding issues.
Comment 9 Jan Becicka 2007-09-19 14:24:26 UTC 
Tomas is file encoding guru :)
Comment 10 Tomas Zezula 2007-09-20 11:49:18 UTC 
The encoding model has dramatically changed in NB 6.0, this issue is no more valid.