Re: Found cause of 46582, what to do?

[Darin Adler <darin bentspoon com>]

On Saturday, May 4, 2002, at 11:59 AM, David Emory Watson wrote:

> > files with a URL using %20 characters or by double-clicking on them.
>
> The user should *definitely* not have to type in an escaped string.

There are *many* filenames that you can only type in as escaped strings. Any filenames with control characters in them in the %01 to %1F range, and filenames with characters in the %80 or higher range that are not part of valid UTF-8 sequences. We don't support the kinds of escaping syntax that is used in the shell for such file names -- instead we fall back on URL syntax.

The tradeoff is simply which of these two features is more important:

    1) Making filenames with trailing spaces fall into the category where you can type the filename without having to fall back on URL syntax.
    2) Repairing the common mistake of copying an extra space when copying a filename from another window, say a terminal, for the vast majority of files that don't have trailing spaces in their names.

I couldn't care less about either feature :-)

    -- Darin