i18n properties: don't convert from UTF-8 to Latin1
Description
Currently the properties files are stored in the UTF-8 and then converted to escaped ISO 8859-1 encoding because use the UTF8 wasn’t properly supported prior Java 9.
In the pom.xml we have a plugin that converts the properties files from UTF-8 to Latin1:
{code}
<plugin>
<!--
Java has trouble reading translations from UTF-8 files. To work around that,
this plugin ensures that Java-compatible encoding is used.
See https://stackoverflow.com/questions/4659929/how-to-use-utf-8-in-resource-properties-with-resourcebundle
-->
<groupId>org.codehaus.mojo</groupId>
<artifactId>native2ascii-maven-plugin</artifactId>
<version>2.0.1</version>
<executions>
<execution>
<id>utf8-to-latin1</id>
<goals>
<goal>inplace</goal>
</goals>
<configuration>
<dir>${project.build.outputDirectory}</dir>
</configuration>
</execution>
</executions>
</plugin>
Since Java 9 this is not a problem anymore and we can simplify the files and avoid the converting step.
Currently the properties files are stored in the UTF-8 and then converted to escaped ISO 8859-1 encoding because use the UTF8 wasn’t properly supported prior Java 9.
In the pom.xml we have a plugin that converts the properties files from UTF-8 to Latin1:
{code}
<plugin> <!-- Java has trouble reading translations from UTF-8 files. To work around that, this plugin ensures that Java-compatible encoding is used. See https://stackoverflow.com/questions/4659929/how-to-use-utf-8-in-resource-properties-with-resourcebundle --> <groupId>org.codehaus.mojo</groupId> <artifactId>native2ascii-maven-plugin</artifactId> <version>2.0.1</version> <executions> <execution> <id>utf8-to-latin1</id> <goals> <goal>inplace</goal> </goals> <configuration> <dir>${project.build.outputDirectory}</dir> </configuration> </execution> </executions> </plugin>Since Java 9 this is not a problem anymore and we can simplify the files and avoid the converting step.