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

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

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