WinSCP; reorder sections

[Imported from Trac: page SftpFrontend, version 43]

SftpFrontend.md

@@ -25,7 +25,23 @@ See the last section of [FTP-and-SFTP.txt]source:docs/frontends/FTP-and-SFTP.txt
 The '`ctime`' and '`mtime`' attributes will always be the same, and are set from the Tahoe `linkmotime` timestamp, which is changed only when the link from the parent directory is modified (see the 'About the metadata' section of [webapi.txt]source:doc/frontends/webapi.txt). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.
 
 
-### sshfs
+### Unicode filenames
+
+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.
+
+Some 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 [mojibake](http://en.wikipedia.org/wiki/Mojibake) for non-ASCII names.
+
+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 [canonically equivalent](http://en.wikipedia.org/wiki/Unicode_equivalence) 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.)
+
+
+### Performance
+
+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.
+
+
+### Specific clients
+
+## sshfs
 
 sshfs 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 [MacFUSE](http://code.google.com/p/macfuse/).
 
@@ -44,7 +60,7 @@ The MacFUSE version of sshfs stores "extended attributes" in files with names st
 On Mac OS X, TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem.
 
 
-### Gnome virtual filesystem (gvfs)
+## Gnome virtual filesystem (gvfs)
 
 [gvfs](https://fedoraproject.org/wiki/Features/Gvfs) is a set of filesystem adapters provided with the Gnome window system. It can be used in two ways: either via the [GIO API](http://library.gnome.org/devel/gio/unstable/), or via a FUSE layer called gvfs-FUSE (not to be confused with sshfs).
 
@@ -55,15 +71,11 @@ gvfs-FUSE, on the other hand, is not recommended for use with Tahoe. This is bec
 It may not be entirely clear to users whether a particular Gnome app is using GIO or gvfs-FUSE. Recent versions of OpenOffice use gvfs-FUSE when opening a file directly from an SFTP filesystem, and this may cause problems (although OpenOffice does appear to work when editing files on an sshfs filesystem).
 
 
-### Unicode filenames
+## WinSCP
 
-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.
+In the WinSCP Login dialog, the following options need to be set (some require 'Advanced options' to be checked):
 
-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 [mojibake](http://en.wikipedia.org/wiki/Mojibake) for non-ASCII names.
+ * In the Environment section, set 'UTF-8 encoding for filenames' to 'On'.
+ * In the Connection section, set 'Server response timeout' to the maximum 6000 seconds.
 
-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 [canonically equivalent](http://en.wikipedia.org/wiki/Unicode_equivalence) 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.)
+Note that these options are not persistent unless you save them as a 'Stored session', together with the host name, username, etc.
-
-
-### Performance
-
-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.