The problem is not with the contents of the file. Its with the name of the
file.
If I upload a file "with file name in multi-byte characters" using a tool
that does not support multi-byte charcters for file names, it creates some
junk file name on server for that file. With this we will have problem if we
want to retrieve the file back, as the name is different from what we have
uploaded.

To test this you can try to upload a file with filename in chinese/japanese
characters.

Thanks,
Nagasekhar

On 1/29/08, Dan Fandrich <dan_at_coneharvesters.com> wrote:
>
> On Tue, Jan 29, 2008 at 10:35:48AM +0530, NAGASEKHAR BHUVANAGIRI wrote:
> > Curl internally reads the file on ftp site while downloading a file, and
> if the
> > file is in multi-byte character format and curl internally does not
> support
> > these characters, it fails to open the file.
>
> curl doesn't interpret the characters in a file at all--it just writes
> them
> as-is into the open file handle you pass in.
>
> > Similarly, while uploading curl
> > creates a file on ftp site.
>
> I'm missing something--curl is supposed to create a file on an ftp site
> when
> it uploads. The name comes from the URL you give it, what ever character
> set you decide to use (no multibyte character set, naturally, as the ftp
> protocol doesn't support that).
>
> >>> Dan
> --
> http://www.MoveAnnouncer.com The web change of address
> service
> Let webmasters know that your web site has moved
>
Received on 2008-01-29