Changes between Version 42 and Version 43 of SftpFrontend


Ignore:
Timestamp:
2010-06-22T20:07:51Z (15 years ago)
Author:
davidsarah
Comment:

WinSCP; reorder sections

Legend:

Unmodified
Added
Removed
Modified

  • SftpFrontend

    v42 v43  
    2626
    2727
    28 === sshfs ===
     28=== Unicode filenames ===
     29
     30The 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.
     31
     32Some clients fail to convert filenames to UTF-8, or require a configuration option to do so; 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.
     33
     34As of Tahoe v1.7.0 final, filenames are normalized to NFC, which means that it is not possible to have two files/subdirectories with [http://en.wikipedia.org/wiki/Unicode_equivalence canonically equivalent] names in the same directory. (This does not cause any incompatibility with filesystems that use a different normalization, such as NFD in Mac OS X.)
     35
     36
     37=== Performance ===
     38
     39The SFTP frontend currently performs no caching (sshfs does cache, but only for 20 seconds with the default settings). Some applications assume that file operations have relatively low latency, and may have very poor performance when working directly with a Tahoe filesystem. In this case it may be better to copy files to a local filesystem and work on them there, then copy back any changes. Note that just browsing a directory may cause some apps to perform many unnecessary reads or attribute checks of files in that directory.
     40
     41
     42=== Specific clients ===
     43
     44== sshfs ==
    2945
    3046sshfs is an SFTP client that allows filesystem access via FUSE (a user-space filesystem layer). It works on Linux and other Unix systems that provide FUSE. For Mac OS X, a patched version of sshfs is included as part of [http://code.google.com/p/macfuse/ MacFUSE].
    … …  
    4561
    4662
    47 === Gnome virtual filesystem (gvfs) ===
     63== Gnome virtual filesystem (gvfs) ==
    4864
    4965[https://fedoraproject.org/wiki/Features/Gvfs gvfs] is a set of filesystem adapters provided with the Gnome window system. It can be used in two ways: either via the [http://library.gnome.org/devel/gio/unstable/ GIO API], or via a FUSE layer called gvfs-FUSE (not to be confused with sshfs).
    … …  
    5672
    5773
    58 === Unicode filenames ===
     74== WinSCP ==
    5975
    60 The 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.
     76In the WinSCP Login dialog, the following options need to be set (some require 'Advanced options' to be checked):
    6177
    62 Some 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.
     78 * In the Environment section, set 'UTF-8 encoding for filenames' to 'On'.
     79 * In the Connection section, set 'Server response timeout' to the maximum 6000 seconds.
    6380
    64 As of Tahoe v1.7.0 final, filenames are normalized to NFC, which means that it is not possible to have two files/subdirectories with [http://en.wikipedia.org/wiki/Unicode_equivalence canonically equivalent] names in the same directory. (This does not cause any incompatibility with filesystems that use a different normalization, such as NFD in Mac OS X.)
    65 
    66 
    67 === Performance ===
    68 
    69 The SFTP frontend currently performs no caching (sshfs does cache, but only for 20 seconds with the default settings). Some applications assume that file operations have relatively low latency, and may have very poor performance when working directly with a Tahoe filesystem. In this case it may be better to copy files to a local filesystem and work on them there, then copy back any changes. Note that just browsing a directory may cause some apps to perform many unnecessary reads or attribute checks of files in that directory.
     81Note that these options are not persistent unless you save them as a 'Stored session', together with the host name, username, etc.