Community
Participate
Working Groups
I've been hit by a problem I guess many people will get hit when they are using xtend. I've been starting my project over in Win32 where the default encoding of the workbench is CP1252, which leads to undesired effects e.g. on Mac because there the default encoding is different and things start to blow up. This is no different than in any other project where one has .java-File but the difference is that xtend uses a high-bit char inside its language (the french quote) whereas in Java the language itself uses on ASCII chars (so one gets only hit if one has none externalized strings) beside that xtend with its multiline strings, ... is a very powerful template language and so having strings inside it makes much more sense than in Java. Take those 2 things together the likeliness of charset problemes in xtend-Files is much bigger compared to standard java. My proposal would be that the New Project-Wizard holds has an additional Drop-Down where one can specify the Project-Encoding (it should probably default to UTF-8).
+1 for the UTF-8 default. This problem hit me twice already (forgot to switch it to UTF-8 after creation). Would be really nice to see it in Xtext.
There is no project wizard for Xtend, so that would only solve the problem for Xtext users. I'm more in favor of a warning (with a quick fix) but only as soon as we have compiler settings in the preferences, so people who explicitly want to use a specific encoding can turn the warning off.
(In reply to comment #2) > There is no project wizard for Xtend, so that would only solve the problem > for Xtext users. Newly created Xtext projects now use UTF-8 as their default encoding. see http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/commit/?id=cc045032ea0bf889f4d0bc4c044a67dc5a8e12fb (In reply to comment #2) > I'm more in favor of a warning (with a quick fix) but only as soon as we > have compiler settings in the preferences, so people who explicitly want to > use a specific encoding can turn the warning off. Bug 383439 addressed this issues, too.
Requested via bug 522520. -M.
