wrong section heading

[Imported from Trac: page SftpFrontend, version 34]
davidsarah 2010-06-17 21:50:59 +00:00
parent 05ea168289
commit 2b722f6b5b

@ -52,7 +52,7 @@ 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). 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).
### Non-Unicode filenames ### 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. Note that SFTP currently does not perform any [Unicode normalization](http://en.wikipedia.org/wiki/Unicode_equivalence) (so for example, filenames copied from a Mac OS X filesystem will remain in NFD); this is likely to change in future. 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. Note that SFTP currently does not perform any [Unicode normalization](http://en.wikipedia.org/wiki/Unicode_equivalence) (so for example, filenames copied from a Mac OS X filesystem will remain in NFD); this is likely to change in future.