Problem with special characters (Umlaute, german)

[der-optimist]

Hello jaymoulin,
I really like your work and I'm 99% happy with it :-)
I live in Germany, so many of the file names I download contain special characters like ä ö ü Ä ß ...
These are shown as a ? in the host system (openmediavault 4.1.16-2) and samba/cifs doesn't show the name at all (it uses 2VH5OD~P.MP4 for example).
I use UTF-8 in openmediavault - what does the jdownloader container use? Or did I just not understand how to set the charset for the container?

Description

Command line I used to start the container
Started via GUI, but according to this command:
docker run -d --restart=always -v ~/Downloads:/root/Downloads -v ~/jdownloader/cfg:/opt/JDownloader/cfg --name jdownloader -u $(id -u):$(id -g) jaymoulin/jdownloader

Steps to reproduce the issue:

1. use openmediavault 4.1.16-2
2. use this docker-container to download a file with a german umlaut (äöüÄÖÜ), e.g.:
   https://www.youtube.com/watch?v=wtJGAJrvFu8

Describe the results you received:
Filenames like "K?ln.mp4" instead of "Köln.mp4"
If I do "mv K?ln.mp4 Köln.mp4" everything is fine, so the special characters work if they are encoded correctly.

(paste logs)

Output of docker inspect jdownloader --format='{{index .Config.Labels.version}}':

0.6.0

Thank you

[jaymoulin]

I don't think this is related to neither docker nor jdownloader, nor my docker-jdownloader image. Do you have something I can make some tests out of?

[der-optimist]

Thank you for your answer. When I copy a file with these characters via cifs or rsync, I do not have this problem. Only with the files downloaded by jdownloader - that's why I searched here. Could you please describe what you need for a test? Maybe you could download the file I linked and see what happens, it contains an ä in the name.What charset/encoding does the docker container use? Or should it take the one of the host system?Thank you!

[jaymoulin]

I cannot reproduce this issue on my machine. Do you know if you use an arm32v6 architecture? If so, your image ID should be c25e336eb651

[der-optimist]

No, I use an Odroid HC1 (same as XU4) with an Exynos 5422 => ARMv7 (Cortex-A15 + Cortex-A7).
Should the docker container use the charset/encoding of the host system or can it be defined separately?

[jaymoulin]

I didn't build an armv7 image. Do you mind giving me the docker image id?

[der-optimist]

Oh ok. I searched google for "jdownloader docker arm" and found your image. As I saw "multiarch, arm, armv7,..." on top of the page, I was happy :-)
I'm not (yet) very familiar with docker - I hope I get the right info for you:

output of "docker images --no-trunc"
REPOSITORY TAG IMAGE ID CREATED SIZE
jaymoulin/jdownloader latest sha256:c25e336eb651600bf100a52f8e6cf40b129277ac6f5614abc4c3f0141300a49e 2 months ago 213MB

output of "docker images"
REPOSITORY TAG IMAGE ID CREATED SIZE
jaymoulin/jdownloader latest c25e336eb651 2 months ago 213MB

[jaymoulin]

You're using the armv6 image which is compatible with armv7. This is the only image that does not use the same base image as the other due to a performance issue with armv6 and latest openjdk with jdownloader. My guess is, something in the base image must be interfering with your encoding.

I don't think I'll spend so much time on recompiling old jdk versions do fix a minor issue like this one but I leave this open for someone to take a look

[der-optimist]

OK thank you