Encoding issue - Githubissues

gpapin commented 4 years ago

Host OS : Ubuntu Docker compose file used to setup the environment:

version: "2"
services:
  calibre:
    image: linuxserver/calibre
    container_name: calibre
    environment:
      - PGID=100
      - PUID=1000
      - TZ=Europe/London
      #- GUAC_USER=abc #optional
      #- GUAC_PASS=900150983cd24fb0d6963f7d28e17f72 #optional
    volumes:
      - ./config:/config
      - /data/ebooks/:/data
    ports:
      - 4080:8080
      - 4081:8081
    restart: unless-stopped

  calibre-web:
    image: linuxserver/calibre-web
    container_name: calibre-web
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/London
      - DOCKER_MODS=linuxserver/calibre-web:calibre #*optional* & **x86-64 only**
    volumes:
      - ./calibre-web:/config
      - /data/ebooks/data:/books
    ports:
      - 8083:8083
    restart: unless-stopped

Let's say I have a file named été.pdf in data: On the host: ls -al /data returns:

-rw-rw-r-- 1 user user    0 Jul 15 20:39 été.pdf

Inside calibre container : ls -al /data returns:

-rw-rw-r-- 1 abc   1000    0 Jul 15 20:39 été.pdf

And yet in calibre when I try to import that file I get this : Screenshot 2019-07-15 20 59 31

I'm not sure where the encoding issue comes from, if guacamole or calibre itself is doing it... Any pointer would be appreciated thanks.

gpapin commented 4 years ago

Thanks, this partially solved the issue, now in the popup I can navigate but when it come to importing the file, calibre still don't understand the é and give me that error:

Screenshot 2019-08-09 09 53 37

aptalca commented 4 years ago

Can you try it with the previous file named été.pdf because those are the characters we tested with. The other file may be having different issues. It's always a good idea to keep the conditions identical when troubleshooting.

gpapin commented 4 years ago

That's a fair point. Unfortunately the issue is the same. I double checked, and from within the container I'm able to rename the file so calibre should have the proper permission to access it. Given the log, it seems that those accents aren't recognised. During your check did you go all the way to the import stage ? because listing the files was working fine. see attachment for reference.