Default Enable --no-unicode-normalization for stickyimport and import backends

[narfa0215]

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/default-enable-no-unicode-normalization-for-stickyimport-and-import-backends/48667

What is the problem you are having with rclone?

When using the stickyimport and import backends, the default Unicode normalization causes issues during file comparisons. This results in certain files not being properly compared, leading to functionality failure in scenarios that require exact file matching. The default behavior interferes with accurate file comparisons when the filenames contain specific characters, causing them to not match as expected.

What is your rclone version (output from rclone version)

rclone v1.68.1

• os/version: slackware 15.0+ (64 bit)
• os/kernel: 6.1.106-Unraid (x86_64)
• os/type: linux
• os/arch: amd64
• go/version: go1.23.1
• go/linking: static
• go/tags: none

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

Unraid, 64 bit

Which cloud storage system are you using? (e.g. Google Drive)

WebDAV

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

rclone backend stickyimport Hasher1: md5 hasher1.md5
rclone check Hasher1: Hasher2: --checksum
rclone --no-unicode-normalization backend stickyimport Hasher1: md5 hasher1.md5

A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)

NOTICE: hasher::Hasher1:: 4 hashes could not be checked

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.