On Mon, 17 Jan 2005, Tony G wrote:

> -B/--use-ascii
>
> First, this option applies to both get and put operations. While that may
> be implied, I think this text could use an explicit reference for file
> updloads.

I'll change the wording to "Enable ASCII transfer when using FTP or LDAP".

> Second, is it an error that stderr is still not in text mode over win32
> after using this option? For example, you can see all output in Notepad but
> Wordpad doesn't see the EOL delimiters. (Maybe I'm twisting up what's meant
> by "text mode".)

Is it? I don't know. No one ever complained, and personally I don't ever use
curl on windows...

> Third, it seems like an anomaly that the format of output should change
> depending on the format of the data being transferred. I would think the
> output should be in a consistent format so that we can code around it and
> not have to look at the type of data being transferred to decide how to
> check for errors, etc.

So what do you suggest? That we never set stdout to text mode in Windows?
Would that have any major side effects to people accustomed to the current
approach?

> Finally, not related to this option but realted to that last point: I'm
> using the -o option to redirect output, and I'm using the command line (both
> win32 and Linux) to direct stderr to a file: "2>filename". But _all_ output
> is going to the stderr file.

You mean the -o file is empty and all data is in 'filename' ? Sounds very odd.
Can you show us a complete command line you use when you see this?

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html