Community
Participate
Working Groups
MacRoman is obsolete, and even before it was obsolete it was pain to use in mixed environment. Nobody sane is using it anymore, at least not consciously, and it causes nothing but encoding problems when it's enabled accidentally. If you're afraid to remove it, at least never ever use it as default (any default other than UTF-8 in modern software is just stupid), and require users to type "I'll never stop using my MC68K Mac!" 20 times before enabling Mac-I-hate-your-accented-characters-Roman.
Sorry, need more specifics. Where do you see explicit MacRoman encoding support?
Indeed, Please change the default file encoding on the MacOS X platform to UTF-8 (as on others actually). MacRoman is obsolete and no longer used on OS X. Having this as the default encoding is bad, before you notice a wrongly encoded file will sneak into a multilingual application. Each time I install a new Eclipse I forget to change this! Preferences->Genera->Workspace->Text file encoding->Default:
(In reply to comment #2) > Indeed, Please change the default file encoding on the MacOS X platform to > UTF-8 (as on others actually). UTF-8 as a default is a hot subject every once in a while, see bug 108668 for details.
Eclipse isn't selecting the default encoding - it comes from the JVM via the "file.encoding" system property. I'm not sure why the Mac JVM is returning MacRoman if as you say it is obsolete. If you write a hello-world Java app that returns the value of System.getProperty("file.encoding") what do you get?
If I run the project on Mac 10.6 with Java 6 I clearly get MacRoman back. But I think this should be clearly UTF-8 not only on Mac! As a solution I suggest starting up the jvm using -Dfile.encoding=UTF-8 in the eclipse.ini.
(In reply to comment #5) > If I run the project on Mac 10.6 with Java 6 I clearly get MacRoman back. > But I think this should be clearly UTF-8 not only on Mac! On my Sun JVM 1.5.0_19 it also returns MacRoman. If it is obsolete, why do jvms return it by default? > As a solution I suggest starting up the jvm using -Dfile.encoding=UTF-8 in the > eclipse.ini. You would have to remember to change it for each Eclipse installation anyway. Marking as a duplicate of bug 108668. *** This bug has been marked as a duplicate of bug 108668 ***
