[tahoe-dev] [tahoe-lafs] #534: "tahoe cp" command encoding issue
andrej at falout.org
Thu Feb 26 08:43:06 UTC 2009
please excuse my crude end-user logic, but here are few observations:
1) Files are on the file system, which thinks they have valid file names.
2) Samba, Windows and CD-ROM/DVD file systems think the same
3) I can backup this files as they are successfully, using many different
backup/Sync tools, including tar, Dropbox, MS Mesh, SyncToy, Unison, rsync
4) I can even back them up using 'tahoe cp' and Tahoe Windows backup client,
and did so several times (I was using this same fileset to test performance)
So I wonder, how come I need to "fix" them to use 'tahoe backup' only?
"ls" and nautilus/konqueror displays gibberish in this particular file, yes,
but when mounted on Windows via Samba, file name is displayed correctly.
I was hoping that the patch had the intention of allowing all valid encoded
file names to be backed up?
On Thu, Feb 26, 2009 at 7:14 PM, Francois Deppierraz <francois at ctrlaltdel.ch
> Andrej Falout wrote:
> > OK, got it running: Is this expected behavior:
> > twisted.python.usage.UsageError: Filename 'Rotha�s Lament.mid' cannot be
> > decoded using the current encoding of your filesystem (UTF-8). Please
> > rename this file.
> Yes, this is expected behavior. It means that this particular filename
> is not encoded with UTF-8 even though your filesystem is configured so.
> I guess that "ls" or nautilus/konqueror also displays gibberish, right ?
> A tool like convmv  might help you to fix your filenames.
>  http://www.j3e.de/linux/convmv/
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
AU: +61 (410) 463 735 NZ: +64 (21) 0256 6825 US: +1 (360) 488 0970
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tahoe-dev