We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clone from - https://bugs.eclipse.org/bugs/show_bug.cgi?id=473682
Hello,
I noticed the l10n tooling generates *.properties files using the encoding specified in Preferences > General > Workspace > Text file encoding.
For instance, when setting this value to UTF-8, all generated files will be in UTF-8 : not only source code, but also the properties files.
This behaviour persist even when specifically associating Java Properties Files with the desired ISO-8859-1 encoding.
As already noticed on the forum efxclipse, it would be better if these file were always encoded in ISO-8859-1, conforming to the specs of the format.
Regards,
Thomas Elskens
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Clone from - https://bugs.eclipse.org/bugs/show_bug.cgi?id=473682
Hello,
I noticed the l10n tooling generates *.properties files using the encoding specified in Preferences > General > Workspace > Text file encoding.
For instance, when setting this value to UTF-8, all generated files will be in UTF-8 : not only source code, but also the properties files.
This behaviour persist even when specifically associating Java Properties Files with the desired ISO-8859-1 encoding.
As already noticed on the forum efxclipse, it would be better if these file were always encoded in ISO-8859-1, conforming to the specs of the format.
Regards,
Thomas Elskens
The text was updated successfully, but these errors were encountered: