From 57a94fed5981bf25fa080ee36abd77c3ed0a4956 Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Tue, 22 Jun 2010 20:13:24 +0000
Subject: [PATCH] assume 1.7.0

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

diff --git a/SftpFrontend.md b/SftpFrontend.md
index 90220d7..a162579 100644
--- a/SftpFrontend.md
+++ b/SftpFrontend.md
@@ -31,7 +31,7 @@ The SFTP frontend encodes all filenames as UTF-8 when communicating with the cli
 
 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.)
+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