Bug 97675 - [Preferences] Pref Page General/Editors/Content Types problems - Default Charset
Summary: [Preferences] Pref Page General/Editors/Content Types problems - Default Cha...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-05-31 15:17 EDT by Sebastian Davids CLA
Modified: 2022-02-21 16:44 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Davids CLA 2005-05-31 15:17:44 EDT
What does the Update button do? -> Tooltip?

Under which circumstances is it enabled?

What does it actually do: if I fill garbage into the text and press Update
nothing happens.

Shouldn't be the text a combo filled with the same values as
General/Editors/Text File Endcoding/Other?
Comment 1 Kim Horne CLA 2005-05-31 15:24:28 EDT
Rafael, is that last point valid?  Could that be a combo or will arbitrary values be acceptable here?
Comment 2 Rafael Chaves CLA 2005-05-31 15:36:58 EDT
The same encoding control used in the resources properties could be used. It
does not restrict valid values to those appearing in the list, it only makes
sure the string is a valid charset name. 

Kim, note that #setDefaultCharset takes anything. If you pass an invalid string,
users will have trouble opening files belonging to that content type. The empty
string is acceptable, and is interpreted by the framework as if the content type
has no default encoding. Null is also acceptable, and means the default encoding
setting is inherited from the base content type (if any).

Ideally, the preference page should allow users to tweak the encoding setting
according to those rules. But I guess this is might be too much work for 3.1.
Comment 3 Susan McCourt CLA 2009-07-09 19:27:25 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:35:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 5 Eclipse Genie CLA 2022-02-21 16:44:06 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.