[tahoe-lafs-trac-stream] [tahoe-lafs] #1089: SFTP and FTP: support for non-UTF-8 charsets (error message "Path could not be decoded as UTF-8") (was: SFTP and FTP: Path could not be decoded as UTF-8)

[tahoe-lafs]

#1089: SFTP and FTP: support for non-UTF-8 charsets (error message "Path could not
be decoded as UTF-8")
-------------------------------+--------------------------------------------
     Reporter:  slush          |       Owner:  nobody                            
         Type:  defect         |      Status:  new                               
     Priority:  minor          |   Milestone:  eventually                        
    Component:  code-frontend  |     Version:  1.7.0                             
   Resolution:                 |    Keywords:  utf-8 unicode ftpd sftp names docs
Launchpad Bug:                 |  
-------------------------------+--------------------------------------------
Changes (by davidsarah):

  * priority:  major => minor


Comment:

 I'm unconvinced that supporting non-UTF-8 encodings is worth the hassle
 and complexity. Does anyone want to argue in favour of it?

 Note that neither SFTP nor FTP have any standard by which a specific non-
 UTF-8 encoding could be automatically negotiated. So, this would have to
 be manually configured. But clients that do a reasonable job of supporting
 non-ASCII characters at all, usually have an option to select UTF-8. So I
 think that support for other encodings would benefit very few users.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1089#comment:12>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage