Community
Participate
Working Groups
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
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.
FYI: dup of bug 108668.
*** This bug has been marked as a duplicate of bug 108668 ***