On 15 Jul 2005, at 22:48, Alexey Proskuryakov wrote:
On Fri, 15 Jul 2005 22:20:36 +0100 Frederick Cheung
<email@hidden> wrote:
I was browsing through the cfnetwork source today and i noticed
that in CFFTPCreateParsedResourceListing whenever it needs to
create a cfstring corresponding to one of the various textual
bits of info in the line it is parsing it uses the encoding
kCFStringEncodingMacRoman. Is there any particular rationale
behind this?
Officially, FTP only supports ASCII.
Actually RFC2640 extends this
I would have expected that UTF8 or ISO-latin-1 would have been
better guesses.
I'd say - the Windows encoding matching user's primary language
(cp1251 in my case).
Good plan
Is this just an oversight?
AFAIK, it's been reported many times, so it's probably not an
oversight. However, Windows users often name files and folders on
FTP with non-ASCII characters, and inability to access them via
Finder is humiliating :(
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.
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
