docs: mention Box as base32768 compatible

As suddenly many people move to Box - another "unlimited" cloud story migration saga there are frequent questions about crypt files encoding to be used.

Box is base32768 friendly.

It has been tested with:

https://pub.rclone.org/base32768.zip

and:

rclone test info --check-length boxremote:

maxFileLength = 255 // for 1 byte unicode characters
maxFileLength = 255 // for 2 byte unicode characters
maxFileLength = 255 // for 3 byte unicode characters
maxFileLength = -1 // for 4 byte unicode characters
This commit is contained in:
kapitainsky 2023-07-18 15:37:41 +01:00 committed by Nick Craig-Wood
parent 8a6bf35481
commit 3a5ffc7839

View File

@ -379,7 +379,7 @@ address this problem to a certain degree.
For cloud storage systems with case sensitive file names (e.g. Google Drive), For cloud storage systems with case sensitive file names (e.g. Google Drive),
`base64` can be used to reduce file name length. `base64` can be used to reduce file name length.
For cloud storage systems using UTF-16 to store file names internally For cloud storage systems using UTF-16 to store file names internally
(e.g. OneDrive, Dropbox), `base32768` can be used to drastically reduce (e.g. OneDrive, Dropbox, Box), `base32768` can be used to drastically reduce
file name length. file name length.
An alternative, future rclone file name encryption mode may tolerate An alternative, future rclone file name encryption mode may tolerate
@ -600,7 +600,7 @@ Properties:
- Encode using base64. Suitable for case sensitive remote. - Encode using base64. Suitable for case sensitive remote.
- "base32768" - "base32768"
- Encode using base32768. Suitable if your remote counts UTF-16 or - Encode using base32768. Suitable if your remote counts UTF-16 or
- Unicode codepoint instead of UTF-8 byte length. (Eg. Onedrive, Dropbox) - Unicode codepoint instead of UTF-8 byte length. (Eg. Onedrive, Dropbox, Box)
#### --crypt-suffix #### --crypt-suffix