tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

assume 1.7.0 

[Imported from Trac: page SftpFrontend, version 46]
davidsarah 2010-06-22 20:13:24 +00:00
parent 9d116354dc
commit 57a94fed59
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
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