Community
Participate
Working Groups
When opening Xtext sources from target platform .source bundles, umlauts in javadocs appear as unknown character. For example in ResourceValidatorImpl. This is annoying, because this character is larger than normal characters and increases the line height in the editor. It might also indicate that the classes are compiled with the wrong encoding; because usually Eclipse handles .source encodings correctly. It might be worth trying to add the encoding to the build.properties as suggested in the attached patch (untested, I don't have a build running here). If I remember correctly, PDE build needs an extra invitation and doesn't use the project encoding.
Created attachment 178225 [details] screenshot.png
Created attachment 178226 [details] 0001-Bug-324534-Set-javacDefaultEncoding-to-ISO-8859-1-in.patch
We have to set the encoding in other build.properties files, too.
I tried the javacDefaultEncoding option but it doensn't change anything. It seems that the standard "jars don't define encoding" problem also applies to source bundles. Unscheduling this bug as there is no simple solution.
setting to won't fix, due to Jan's comment. Please reopen with a solution to that problem.