From 2b722f6b5b5544e63358c3b3addf7365799a29ab Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Thu, 17 Jun 2010 21:50:59 +0000
Subject: [PATCH] wrong section heading

[Imported from Trac: page SftpFrontend, version 34]
---
 SftpFrontend.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SftpFrontend.md b/SftpFrontend.md
index e485193..e375743 100644
--- a/SftpFrontend.md
+++ b/SftpFrontend.md
@@ -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).
 
 
-### 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.