Re: CFFTPCreateParsedResourceListing text encoding
Re: CFFTPCreateParsedResourceListing text encoding
- Subject: Re: CFFTPCreateParsedResourceListing text encoding
- From: Frederick Cheung <email@hidden>
- Date: Sat, 16 Jul 2005 11:13:35 +0100
On 16 Jul 2005, at 10:37, Alexey Proskuryakov wrote:
On Fri, 15 Jul 2005 23:02:45 +0100 Frederick Cheung
<email@hidden> wrote:
Officially, FTP only supports ASCII.
Actually RFC2640 extends this
Thanks, I somehow managed to miss that... However, this RFC is
(understandably) focused on UTF-8, which I have never seen used in
real life yet.
I've seen it used, but perhaps not exactly in the way intended by the
RFC (certainly not indicated in response to the FEAT command). In
general servers just seem to send whatever comes out of /bin/ls
(forgetting to encode \n in file names grrr), if that happens to be
UTF8 so be it.
It doesn't look like it would work with the ftp server built into
Mac OS X either, as that certainly seems to be using utf8. Oh well.
Uh-oh... Thankfully, several 3rd party FTP clients support
windows-1251 (and other 8-bit encodings), but sounds like we're out
of luck when it comes to CFFTP and Finder.
Providing a user override is another option I suppose. In the end
I've been using CFFTPCreateParsedResourceListing but using ftpparse
(http://cr.yp.to/ftpparse.html) to get filenames out and for handling
formats that CFFTPCreateParsedResourceListing doesn't understand
(EPLF and so on)
Fred
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden