[tahoe-dev] [tahoe-lafs] #731: what to do with filenames that are illegal on some systems
tahoe-lafs
trac at tahoe-lafs.org
Wed Jul 14 06:30:27 UTC 2010
#731: what to do with filenames that are illegal on some systems
-------------------------------+--------------------------------------------
Reporter: zooko | Owner:
Type: defect | Status: new
Priority: major | Milestone: eventually
Component: code-dirnodes | Version: 1.4.1
Resolution: | Keywords: forward-compatibility i18n unicode names
Launchpad Bug: |
-------------------------------+--------------------------------------------
Comment (by zooko):
(copying some comments that I wrote over on #1072...)
It is worth considering the five possible Requirements in [http://tahoe-
lafs.org/pipermail/tahoe-dev/2009-May/001670.html this] message. With our
current unicode support as of Tahoe-LAFS v1.7.0 we have achieved
Requirement 1 (unicode), Requirement 2 (faithful if unicode). We have not
achieved Requirement 3 (no file left behind), Requirement 4 (faithful
bytes if not unicide), or Requirement 5 (no loss of information).
Nowadays I am pretty skeptical of the value of Requirement 4.
After I wrote that message I subsequently realized that a good behavior
would be that if you load an ill-encoded filename into Tahoe-LAFS then its
representation looks identical to or similar to the representation of that
file when you view it with Nautilus, GNU ls, or whatever other tools would
have the same problem with ill-encoded filenames. I think this should be
added as Requirement 6 (familiar gibberish): "If you copy an ill-encoded
filename into Tahoe-LAFS, its filename looks identical to or similar to
what you see when you view it with other tools (e.g. Nautilus, GNU ls,
etc.)".
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/731#comment:14>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list