Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 171087 - [Encoding] [Preferences] default encoding for Windows should be more standard
Summary: [Encoding] [Preferences] default encoding for Windows should be more standard
Status: RESOLVED DUPLICATE of bug 108668
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-19 14:54 EST by Tom Roche CLA
Modified: 2007-01-22 10:42 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Roche CLA 2007-01-19 14:54:49 EST
Build ID: I20061214-1445

Please make the default workspace encoding (i.e. Preferences>General>
Workspace>Text file encoding) for Windows more standard.

Cp1252 is not, strictly speaking, a standard encoding: it is at best a
"proprietary standard," the use of which made sense when few tools
supported more standard encodings, notably Unicode (e.g. UTF-8 or
UTF-16). That is no longer the case (e.g. Unicode support is
widespread); yet, at least as of 3.3-M4, Cp1252 remains the Eclipse
default for Windows.

Steps To Reproduce:

0 Pull down a vanilla Eclipse for win32.

1 Create a java file. Add a symbol which has a non-standard encoding
  in Cp1252 (empirically, copyright and Microsoft quotes are the major
  offenders).

2 Submit the file to a build with a compiler which expects a standard
  encoding (e.g. IBM's).

3 Result: something like

> <int/>. ERROR in <path to your file>
> Cannot read the source from <path to your file>; either the file uses a different encoding than UTF-8 or it is corrupted
Comment 1 Dani Megert CLA 2007-01-21 10:17:52 EST
As far as I know Eclipse does not set a default but uses the 'file.encodin' property. So, the question is, why does the VM not set the file.encoding to UTF-8 but cp1252 on Windows - even though I've set my code page to be 65001 (UTF-8)?

Moving to the correct owner of this.
Comment 2 Dani Megert CLA 2007-01-21 11:48:53 EST
FYI: dup of bug 108668.
Comment 3 John Arthorne CLA 2007-01-22 10:42:20 EST

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