Changes between Version 35 and Version 36 of SftpFrontend


Ignore:
Timestamp:
2010-06-17T21:53:27Z (15 years ago)
Author:
davidsarah
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SftpFrontend

    v35 v36  
    5757The SFTP frontend encodes all filenames as UTF-8 when communicating with the client. Support for displaying and copying non-ASCII filenames is likely to vary between clients. If you are using a filesystem that represents names as UTF-8 (including via sshfs), then it should just work, but please report your experience with this. Note that SFTP currently does not perform any [http://en.wikipedia.org/wiki/Unicode_equivalence Unicode normalization] (so for example, filenames copied from a Mac OS X filesystem will remain in NFD); this is likely to change in future.
    5858
    59 Many clients do not convert filenames to UTF-8; see ticket #1089. In this case they will usually fail to create non-ASCII filenames (although there is a small chance that the name in another encoding will accidentally be decodable as UTF-8), and directory listings will show [http://en.wikipedia.org/wiki/Mojibake mojibake] for non-ASCII names.
     59Some clients fail to convert filenames to UTF-8; see ticket #1089. In this case they will usually fail to create non-ASCII filenames (although there is a small chance that the name in another encoding will accidentally be decodable as UTF-8), and directory listings will show [http://en.wikipedia.org/wiki/Mojibake mojibake] for non-ASCII names.
    6060
    6161