Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 97308 - [Preferences] "New text file encoding / line delimiter" preferences should be on General > Workspace
Summary: [Preferences] "New text file encoding / line delimiter" preferences should be...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M2   Edit
Assignee: shujie liao CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-30 12:26 EDT by Markus Keller CLA
Modified: 2005-10-18 07:49 EDT (History)
2 users (show)

See Also:

Attachments
A patch for 97308 (10.80 KB, patch)
2005-08-19 09:32 EDT, shujie liao CLA 		no flags Details | Diff
View All 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 Markus Keller CLA 2005-05-30 12:26:55 EDT 
I20050527-1300

On Preferences > General > Editors, there are two preferences that don't really
belong there: "New text file encoding" and "New text file line delimiter" are
also applicable without editors and should therefore be on General > Workspace.
Comment 1 shujie liao CLA 2005-08-19 09:32:28 EDT 
Created attachment 26291 [details]
A patch for 97308

Apply against /org.eclipse.ui.ide/src/org/eclipse/ui/
Comment 2 Tod Creasey CLA 2005-08-22 10:29:46 EDT 
Patch released for build >20050822
Comment 3 Kim Horne CLA 2005-09-20 15:51:16 EDT 
Verified in I20050920-0010
Comment 4 Missing name CLA 2005-10-17 20:31:17 EDT 
3.2M2 documentation still talks about encoding and delimiter being under Editor
preferences. This is misleading and frustrating. It took me a while to realise
this has been moved. 

Using encoding or delimiter as preference filter also does not show the new
workspace level preference settings.

In our projects inconsistent documentation is treated as bug and is clubbed with
the original feature/bug. 

Should I reopen this bug ?
Comment 5 Tod Creasey CLA 2005-10-18 07:49:03 EDT 
No - please open a bug against doc