On 21 November 2012 17:35, Paul Wiseman <<a href="mailto:poalman@gmail.com">poalman@gmail.com</a>> wrote:<br>><br>> I know this has been asked before, I've found it in several trackers.<br>><br>> <a href="http://twistedmatrix.com/trac/ticket/5411">http://twistedmatrix.com/trac/ticket/5411</a><br>
> <a href="http://twistedmatrix.com/trac/ticket/4515">http://twistedmatrix.com/trac/ticket/4515</a><br>> <a href="http://twistedmatrix.com/trac/ticket/5100">http://twistedmatrix.com/trac/ticket/5100</a><br>><br>> Some of these were created a while ago, some with patches. I wondered what the current status was with regards to utf-8 in ftp? Is it currently possible?<br>
><br>> I'm trying to list a folder called 'Paul’s Mac Pro', this gets returned as 'Paulâ s Mac Pro'. The client tries to list that folder, and the server returns 'Paulâ  s Mac Pro: No such file or directory.' I think the client is interpreting the bytes that make up the unicode char as separate ascii characters. (maybe a problem with the client? FileZilla 3.6.0.1)<br>
><br>> This problem may be made worse by my implementation of IFTPShell, I can try to make an example if this isn't the expected result.<br>><br>> I'm returning all names and paths back encoded in utf-8, but maybe the problem is the client isn't expecting it because there's no FEAT command (is the patch in 4515 ok to add?)<br>
><br>> I just want to get an idea of how I can best go about getting this to work. Will I need to build in support, or is it available in a newer version, or by applying some patches?<br>><br>> Thanks very much!!<br>
><br>> Paul<br><br><font face="courier new, monospace">>>> a= "Paulâ s Mac Pro" #This is what the client gets<br>>>> <br>>>> a<br>'Paul\xc3\xa2\xc2\x80\xc2\x99s Mac Pro'<br>
>>> a.decode("utf-8")<br>u'Paul\xe2\x80\x99s Mac Pro' #utf-8 encoding in a unicode string???<br>>>> <br>>>> b= u"Paul’s Mac Pro"<br>>>> b.encode("utf-8")<br>
'Paul\xe2\x80\x99s Mac Pro'<br>>>> </font><br><div><font face="courier new, monospace"><br></font></div><div><font face="arial, helvetica, sans-serif">So I'm not sure exactly what's happening here, but it's like path has been encoded twice. Bit confused as to how this could be happening!</font></div>