Menu

#299 Failure to Read umlauts in wrapper configuration file

v3.5.23
open
nobody
5
2017-07-05
2017-07-05
Bidrohi
No

Dear java service wrapper team,
I have encountered following problem when reading the properties via the WrapperManager.getProperties():
The conf File is encoded with the default system encoding and contains umlauts, but the java string returned by the WrapperManager returns contains different characters.
I tried to write the conf in UTF-8 and use the #enconding=UTF-8 option with the same result(even the same wrong characters).
The option used is wrapper.logfile with the value D:/release8.38ä_ö_ü_ß_À_Á_Â_Ã_Ä_Å_Æ_Ç_È_É_Ê_Ë_Ì_Í_Î_Ï_Ð_Ñ_Ò_Ó_Ô_Õ_Ö_ר_Ù_Ú_Û_Ü_Ý_Þ_ß_à_á_â_ã_ä_å_æ_ç_è_é_ê_ë_ì_í_î_ï_ð_ñ_ò_ó_ô_õ_ö÷_ø_ù_ú_û_ü_ý_þ_ÿ/SCU_wrapper.log

and the WrapperManager yields
D:/release8.38„á·µÇ_ŽÔÒ_Ó_Þ_Öר_Ñ¥ã_à_â_åžë_é_ê_š_í_è_á _ƒ_Ƈ_Šˆ¡ŒÐ¤¢“_äö£ì_ç˜/SCU_wrapper.log

When the file is encoded in UTF-8 and #encoding=UTF-8 ist used instead of default:
D:/release8.38„á·µÇ_ŽÔÒ_Ó_Þ_Öר_Ñ¥ã_à_â_åžë_é_ê_š_í_è_á _ƒ_Ƈ_Šˆ¡ŒÐ¤¢“_äö£ì_ç˜/SCU_wrapper.log

is returned.

The above sequenz of used characters(after the ß) is a continuous block from 8859-1 in order to identify any pattern in the encoding.(I couldnt find one)

with kind regards and thank you for your help

Discussion


Log in to post a comment.

MongoDB Logo MongoDB