From 037a6bd1b06d1c5eaaf8411e9c3a0ea29b773d16 Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Wed, 5 Apr 2023 11:29:49 +0100 Subject: [PATCH] crypt: recommend Dropbox for base32768 encoding See: https://forum.rclone.org/t/base32768-filename-encoding-with-crypt-dropbox-remote/37375 --- backend/crypt/crypt.go | 2 +- docs/content/crypt.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/backend/crypt/crypt.go b/backend/crypt/crypt.go index ce200801c..641d6642f 100644 --- a/backend/crypt/crypt.go +++ b/backend/crypt/crypt.go @@ -147,7 +147,7 @@ length and if it's case sensitive.`, }, { Value: "base32768", - Help: "Encode using base32768. Suitable if your remote counts UTF-16 or\nUnicode codepoint instead of UTF-8 byte length. (Eg. Onedrive)", + Help: "Encode using base32768. Suitable if your remote counts UTF-16 or\nUnicode codepoint instead of UTF-8 byte length. (Eg. Onedrive, Dropbox)", }, }, Advanced: true, diff --git a/docs/content/crypt.md b/docs/content/crypt.md index 4a5eca211..bb2f58c3a 100644 --- a/docs/content/crypt.md +++ b/docs/content/crypt.md @@ -379,7 +379,7 @@ address this problem to a certain degree. For cloud storage systems with case sensitive file names (e.g. Google Drive), `base64` can be used to reduce file name length. For cloud storage systems using UTF-16 to store file names internally -(e.g. OneDrive), `base32768` can be used to drastically reduce +(e.g. OneDrive, Dropbox), `base32768` can be used to drastically reduce file name length. An alternative, future rclone file name encryption mode may tolerate