Bug 26035 - Local history uses wrong character encoding
Summary: Local history uses wrong character encoding
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Andre Weinand CLA
QA Contact:
URL:
Whiteboard:
Keywords: nl
Depends on:
Blocks:
 
Reported: 2002-11-12 07:57 EST by Roy Lee CLA
Modified: 2003-02-14 11:04 EST (History)
1 user (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 Roy Lee CLA 2002-11-12 07:57:47 EST 
i set the windows->preferences->editors->TextFileEncoding to GBK
it a Chinese charactor set.and then i wrote some Chinese in the println method 
just as System.out.println("²Ù×÷ʧ°Ü"); after some modify,i replace this code 
back from Local History.a mistake appeared.it left a mess in the println 
sentence.the same mistake appear in WebSphere Application Developer 5.0
Comment 1 Nick Edgar CLA 2002-11-12 08:15:26 EST 
Noticed that org.eclipse.compare.internal.Utilities.readString does not honour 
the workbench encoding (ResourcesPlugin.getEncoding()).

When showing local history items, Compare should use the workbench encoding.

When restoring items, though, it should just restore the bytes that were saved 
in the local history.  Encodings should not come into play at all.
Comment 2 Andre Weinand CLA 2003-02-14 11:04:31 EST 
fixed and released for I20030218