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

[Imported from Trac: page SftpFrontend, version 36]

davidsarah 2010-06-17 21:53:27 +00:00
parent 7c69b74672
commit 552808dcaf
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

@ -56,7 +56,7 @@ It may not be entirely clear to users whether a particular Gnome app is using GI
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.
Many clients do not 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.
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.
### Performance