Using UTF-8 in Jtwig with translation property-files












1















I have 4 locales in my resources folder which I'm loading exactly as shown in this example: https://github.com/jtwig/jtwig-examples/blob/master/gradle-jtwig-translate-extension-properties/src/main/java/org/jtwig/example/translate/SimpleAppWithTranslate.java



However the properties are not loaded with the correct encoding.



E.g. the German Grüsse from the property file becomes Grüsse once loaded via Jtwig's PropertiesLocalizedMessageResourceLoader. It happens in this part of the example code:



propertiesMessageSource()
.withLookupClasspath("translations")
.build()


Is there an easy way to load the property files in UTF-8 using something like the code from the link above?



P.S. I'm using Java 11










share|improve this question























  • You can't, because properties files are required to be encoded in ISO 8859-1 as specified in the javadoc of Properties.read(InputStream)

    – Thomas Fritsch
    Nov 21 '18 at 13:30













  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.

    – Thomas Fritsch
    Nov 21 '18 at 13:39











  • @ThomasFritsch thanks, that's what I'm currently doing as a work-around, I was hoping I could avoid that.

    – emazzotta
    Nov 21 '18 at 13:40
















1















I have 4 locales in my resources folder which I'm loading exactly as shown in this example: https://github.com/jtwig/jtwig-examples/blob/master/gradle-jtwig-translate-extension-properties/src/main/java/org/jtwig/example/translate/SimpleAppWithTranslate.java



However the properties are not loaded with the correct encoding.



E.g. the German Grüsse from the property file becomes Grüsse once loaded via Jtwig's PropertiesLocalizedMessageResourceLoader. It happens in this part of the example code:



propertiesMessageSource()
.withLookupClasspath("translations")
.build()


Is there an easy way to load the property files in UTF-8 using something like the code from the link above?



P.S. I'm using Java 11










share|improve this question























  • You can't, because properties files are required to be encoded in ISO 8859-1 as specified in the javadoc of Properties.read(InputStream)

    – Thomas Fritsch
    Nov 21 '18 at 13:30













  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.

    – Thomas Fritsch
    Nov 21 '18 at 13:39











  • @ThomasFritsch thanks, that's what I'm currently doing as a work-around, I was hoping I could avoid that.

    – emazzotta
    Nov 21 '18 at 13:40














1












1








1








I have 4 locales in my resources folder which I'm loading exactly as shown in this example: https://github.com/jtwig/jtwig-examples/blob/master/gradle-jtwig-translate-extension-properties/src/main/java/org/jtwig/example/translate/SimpleAppWithTranslate.java



However the properties are not loaded with the correct encoding.



E.g. the German Grüsse from the property file becomes Grüsse once loaded via Jtwig's PropertiesLocalizedMessageResourceLoader. It happens in this part of the example code:



propertiesMessageSource()
.withLookupClasspath("translations")
.build()


Is there an easy way to load the property files in UTF-8 using something like the code from the link above?



P.S. I'm using Java 11










share|improve this question














I have 4 locales in my resources folder which I'm loading exactly as shown in this example: https://github.com/jtwig/jtwig-examples/blob/master/gradle-jtwig-translate-extension-properties/src/main/java/org/jtwig/example/translate/SimpleAppWithTranslate.java



However the properties are not loaded with the correct encoding.



E.g. the German Grüsse from the property file becomes Grüsse once loaded via Jtwig's PropertiesLocalizedMessageResourceLoader. It happens in this part of the example code:



propertiesMessageSource()
.withLookupClasspath("translations")
.build()


Is there an easy way to load the property files in UTF-8 using something like the code from the link above?



P.S. I'm using Java 11







java encoding utf-8 internationalization jtwig






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 13:21









emazzottaemazzotta

67711018




67711018













  • You can't, because properties files are required to be encoded in ISO 8859-1 as specified in the javadoc of Properties.read(InputStream)

    – Thomas Fritsch
    Nov 21 '18 at 13:30













  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.

    – Thomas Fritsch
    Nov 21 '18 at 13:39











  • @ThomasFritsch thanks, that's what I'm currently doing as a work-around, I was hoping I could avoid that.

    – emazzotta
    Nov 21 '18 at 13:40



















  • You can't, because properties files are required to be encoded in ISO 8859-1 as specified in the javadoc of Properties.read(InputStream)

    – Thomas Fritsch
    Nov 21 '18 at 13:30













  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.

    – Thomas Fritsch
    Nov 21 '18 at 13:39











  • @ThomasFritsch thanks, that's what I'm currently doing as a work-around, I was hoping I could avoid that.

    – emazzotta
    Nov 21 '18 at 13:40

















You can't, because properties files are required to be encoded in ISO 8859-1 as specified in the javadoc of Properties.read(InputStream)

– Thomas Fritsch
Nov 21 '18 at 13:30







You can't, because properties files are required to be encoded in ISO 8859-1 as specified in the javadoc of Properties.read(InputStream)

– Thomas Fritsch
Nov 21 '18 at 13:30















You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.

– Thomas Fritsch
Nov 21 '18 at 13:39





You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.

– Thomas Fritsch
Nov 21 '18 at 13:39













@ThomasFritsch thanks, that's what I'm currently doing as a work-around, I was hoping I could avoid that.

– emazzotta
Nov 21 '18 at 13:40





@ThomasFritsch thanks, that's what I'm currently doing as a work-around, I was hoping I could avoid that.

– emazzotta
Nov 21 '18 at 13:40












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412992%2fusing-utf-8-in-jtwig-with-translation-property-files%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412992%2fusing-utf-8-in-jtwig-with-translation-property-files%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents