Bug 21303 - Save does not use specified encoding
Summary: Save does not use specified encoding
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.0   Edit
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 21167 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-07-08 10:21 EDT by Nick Edgar CLA
Modified: 2003-02-10 06:24 EST (History)
5 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 Nick Edgar CLA 2002-07-08 10:21:36 EDT 
R2.0

When you save a file, it always uses the workbench encoding, which will be 
different than the encoding chosen by the user via Edit / Encoding.
This can result in loss of data.
It should save the file in the same encoding as shown in Edit / Encoding.

Saving files using different encodings can result in problems for the Java 
builder, since it assumes all .java files use the same encoding (the workbench 
encoding).
However, that is what the user asked for.
The user may well use the workbench encoding for all .java files, but use 
different encodings for other files (e.g. UTF-8 for XML files).

See also newsgroup thread "about Japanese Encode".
Comment 1 Bob Foster CLA 2002-08-09 23:06:40 EDT 
It's kind of ugly what you have to do to fix this in a subclass, too. All
encoding-related behavior should be neatly broken out.
Comment 2 Kai-Uwe Maetzel CLA 2002-09-12 04:24:44 EDT 
*** Bug 21167 has been marked as a duplicate of this bug. ***
Comment 3 Kai-Uwe Maetzel CLA 2003-02-10 06:24:35 EST 
This is in since M4.