No subject

to restore the previous state (and meaningfulness) of files and
directories so i don't think it should stop when backupping weird
filenames that i can't decode without errors to unicode, but instead
save the filename with the unicode aware charset by replacing or
escaping and maybe add a note somewhere containing the readed fs
bytestring. Where, i still don't know. Maybe it's worth to remember that
json directory metadata are encoded to utf-8 as well on the wire.

my two cents.

Alberto