How to disable unicode normalization in config?

Help and Support
1

What is the problem you are having with rclone?

I would like to disable unicode normalization in the configuration, i.e. enable the option –no-unicode-normalization via config.

Run the command 'rclone version' and share the full output of the command.

rclone v1.71.2

  • os/version: Microsoft Windows 10 IoT Enterprise LTSC 2021 21H2 21H2 (64 bit)
  • os/kernel: 10.0.19044.6456 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.25.3
  • go/linking: static
  • go/tags: cmount

Which cloud storage system are you using? (eg Google Drive)

N/A

The command you were trying to run (eg rclone copy /tmp remote:tmp)

mkdir test_NFC
touch test_NFC/で
mkdir test_NFD
touch test_NFD/で
rclone sync test_NFC test_NFD --progress

The first character で has NFC normalization whereas the second one で has NFD normalization.

With normalization:

rclone sync test_NFC test_NFD --progress
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Checks:                 1 / 1, 100%
Elapsed time:         0.0s

without normalization:

rclone sync test_NFC test_NFD --progress --no-unicode-normalization
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Checks:                 1 / 1, 100%
Deleted:                1 (files), 0 (dirs)
Transferred:            1 / 1, 100%
Elapsed time:         0.0s

Is there a way to enable --no-unicode-normalization from the config?

2

No.

Config file only contains remotes’ specific flags but --no-unicode-normalizationis a global one.

As an alternative you can specify it in environment variable.

$ export RCLONE_NO_UNICODE_NORMALIZATION="TRUE"
3

Whoops, I missed that in the docs! Sorry for that and thanks.

4

you never posted the config file?

might try adding the following line to the remote in the config file.
override.no-unicode-normalization = true

5

This is interesting… Have to admit that never used it.

And not entirely sure about difference between override.var and global.var…

6

you never posted the config file?

I didn’t think there was a need, because I was trying to get it to work for arbitrary remotes (local, sftp, webdav, etc).

override.no-unicode-normalization = true does not work for me, at least when syncing from local windows to remote sftp. But I now actually prefer the environment variable over having to enable this for each individual remote. I don’t see a reason to keep normalization enabled.

7

then could add global.no-unicode-normalization = true in the config file

the good thing, rclone is very flexible, often more than one way to get the same task done

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.