Bug 61986 - [encoding] should file states remember encoding?
Summary: [encoding] should file states remember encoding?
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 59232
  Show dependency tree
 
Reported: 2004-05-12 15:30 EDT by Rafael Chaves CLA
Modified: 2006-11-21 14:00 EST (History)
2 users (show)

See Also:

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 Rafael Chaves CLA 2004-05-12 15:30:42 EDT 
IFileState extends IEncodedStorage. How should IFileState#getCharset work?

Some approaches:

a) remember the encoding for the file when it was saved (maybe only if one was
set by the user - either at the file or the container level)
b) guess it using the content type manager
c) do a), then b) if needed

"a)" would require the file history to be enhanced to support encoding info.

One thing to remember is that the target file may not exist in the workspace.
Comment 1 Rafael Chaves CLA 2004-05-27 16:39:45 EDT 
Andre, it is very unlikely we are going to fix this one. It maight cause a
considerable overhead in the history story, only to support the not very common
scenario of people changing file encodings and being interested in the previous
contents.
Comment 2 Rafael Chaves CLA 2004-06-03 16:24:50 EDT 
Deferring. Investigate post-3.0.
Comment 3 John Arthorne CLA 2006-11-21 14:00:44 EST 
Closing as won't fix.