[GH-ISSUE #2519] Non latin characters in names not supported #1232

New issue

Closed

opened 2026-03-04 01:52:26 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:52:26 +03:00

Owner

Originally created by @fr33z00 on GitHub (Aug 27, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2519

Additional Information

Version of s3fs being used (`s3fs --version`)

V1.90 (commit:unknown) with GnuTLS(gcrypt) [as of debian packages]

Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)

libfuse2/stable,now 2.9.9-6+b1 amd64
libfuse3-3/stable,now 3.14.0-4 amd64

Kernel information (`uname -r`)

6.1.0-23-amd64

GNU/Linux Distribution, if applicable (`cat /etc/os-release`)

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian

Details about issue

Non Latin characters in objects names lead to messy names. Example:
Книга1.xlsx => ''$'\320\232\320\275\320\270\320\263\320\260''1.xlsx'

I did not even figured out what is the relation between theses numbers and unicode hexadecimal values.

Originally created by @fr33z00 on GitHub (Aug 27, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2519  ### Additional Information #### Version of s3fs being used (`s3fs --version`) V1.90 (commit:unknown) with GnuTLS(gcrypt) [as of debian packages] #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) libfuse2/stable,now 2.9.9-6+b1 amd64 libfuse3-3/stable,now 3.14.0-4 amd64 #### Kernel information (`uname -r`) 6.1.0-23-amd64 #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian ### Details about issue Non Latin characters in objects names lead to messy names. Example: `Книга1.xlsx` => `''$'\320\232\320\275\320\270\320\263\320\260''1.xlsx'` I did not even figured out what is the relation between theses numbers and unicode hexadecimal values.

kerem closed this issue

2026-03-04 01:52:26 +03:00

kerem commented

2026-03-04 01:52:26 +03:00

Author

Owner

@fr33z00 commented on GitHub (Aug 29, 2024):

As an answer to my own issue, this does not come from s3fs.
The fix consists in generating the locales UTF-8. I did not mention, and should have, that I was working into a docker container.

@fr33z00 commented on GitHub (Aug 29, 2024): As an answer to my own issue, this does not come from s3fs. The fix consists in generating the locales UTF-8. I did not mention, and should have, that I was working into a docker container.

kerem referenced this issue

2026-03-04 02:02:36 +03:00

[PR #1232] [MERGED] Not trap chown command errors directly #1876