Changes between Initial Version and Version 15 of Ticket #731


Ignore:
Timestamp:
2011-07-21T18:26:12Z (13 years ago)
Author:
zooko
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #731

    • Property Keywords forward-compatibility i18n unicode names added
    • Property Milestone changed from 1.5.0 to eventually

  • Ticket #731 – Description

    initial v15  
    773.  The filename could case-collide with another filename in the same directory, and system B could be a case-insensitive filesystem.  (Note that Tahoe's current naïve approach will result in a randomly-chosen one of the files overwriting the other if the target system is Windows or Macintosh.)
    88
    9 4.  If we allowed undecodable bytestring filenames from POSIX system A's, either by storing bytestring (non-unicode) filenames, or by some escaping mechanism such as {{{utf8b}}}, then a non-POSIX
    10 system B would not be able to accept that name (or at least we ''should'' not write that name into that system).  Likewise some users of POSIX have a policy that only correctly encoded unicode filenames should be stored in their filesystem, so for them we should not write that name even though we can do so by using the POSIX byte-oriented APIs.
     94.  If we allowed undecodable bytestring filenames from POSIX system A's, either by storing bytestring (non-unicode) filenames, or by some escaping mechanism such as {{{utf8b}}}, then a non-POSIX system B would not be able to accept that name (or at least we ''should'' not write that name into that system).  Likewise some users of POSIX have a policy that only correctly encoded unicode filenames should be stored in their filesystem, so for them we should not write that name even though we can do so by using the POSIX byte-oriented APIs.
    1110
    1211Here are someone else's notes about these sorts of issues: