Using UTF-8 in Jtwig with translation property-files











up vote
1
down vote

favorite












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






















  • 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 at 13:30












  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.
    – Thomas Fritsch
    Nov 21 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 at 13:40















up vote
1
down vote

favorite












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






















  • 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 at 13:30












  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.
    – Thomas Fritsch
    Nov 21 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 at 13:40













up vote
1
down vote

favorite









up vote
1
down vote

favorite











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













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




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 at 13:21









emazzotta

6101917




6101917












  • 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 at 13:30












  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.
    – Thomas Fritsch
    Nov 21 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 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 at 13:30












  • You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.
    – Thomas Fritsch
    Nov 21 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 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 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 at 13:30














You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.
– Thomas Fritsch
Nov 21 at 13:39




You need to use escaping in properties file, e.g. Gru00FCe instead of Grüsse.
– Thomas Fritsch
Nov 21 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 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 at 13:40

















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',
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






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


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

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
Read more

Calculate evaluation metrics using cross_val_predict sklearn

Image
1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79 ...
Read more

Insert data from modal to MySQL (multiple modal on website)

Image
0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document"> ...
Read more