From 835b6761b77babb8cada2370f7e981431946cb18 Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Sun, 21 Feb 2016 14:09:06 +0000 Subject: [PATCH] Write about convmv in the docs for fixing non UTF-8 filesystems - fixes #300 --- docs/content/local.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/content/local.md b/docs/content/local.md index 7e7006e3f..28f8a0715 100644 --- a/docs/content/local.md +++ b/docs/content/local.md @@ -25,9 +25,13 @@ on OS X. ### Filenames ### Filenames are expected to be encoded in UTF-8 on disk. This is the -normal case for Windows and OS X. There is a bit more uncertainty in -the Linux world, but new distributions will have UTF-8 encoded files -names. +normal case for Windows and OS X. + +There is a bit more uncertainty in the Linux world, but new +distributions will have UTF-8 encoded files names. If you are using an +old Linux filesystem with non UTF-8 file names (eg latin1) then you +can use the `convmv` tool to convert the filesystem to UTF-8. This +tool is available in most distributions' package managers. If an invalid (non-UTF8) filename is read, the invalid caracters will be replaced with the unicode replacement character, '�'. `rclone`