Bug 81637

Summary:	CVS compare uses wrong character encoding
Product:	[Eclipse Project] Platform	Reporter:	Stefan Tannenbaum <eclipse.20.stannenbaum>
Component:	Compare	Assignee:	Platform-Compare-Inbox <platform-compare-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse.20.stannenbaum
Version:	3.1
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Stefan Tannenbaum

2004-12-20 04:01:55 EST

I frequently compare local sourcefiles with the latest versions from our CVS repository, mostly by 
double clikcing a conflict in the synchronize perspective.

The compare editor then loads the local file using the specified character encoding for this file (in my 
case latin1) and the remote file using the default character encoding of the workbench (in my case utf
-8). The result is a scrambled remote file and a lot of false positive changes.

The remote file should always be read in the same character encoding as the local file.

Setting the default character encoding of the workbench to latin1 has helped for my project, but this 
was not obvious and took me some weeks to discover. It is also a problem if two different encodings 
are used frequently.

Comment 1 Andre Weinand

2005-01-06 12:06:20 EST


*** This bug has been marked as a duplicate of 72995 ***