Re: piping find to zip -- with spaces in path

["Dan B." <danb@kempt.net>]

Bob Proulx wrote:
> Bob Proulx wrote:
...
> So as you can see whitespace isn't safe to use in URLs.  This is
> basically the same as for Unix filenames.

They're not quite the same:


In URIs, it's not that whitespace "isn't safe to use"; it's simply
that whitespace is not allowed, period.  (Yes, encodings of whitespace
characters are allowed, but that encoding still contains no actual
whitespace characters.)

That's clearly defined by a specification (IETF RFC 3986 _Uniform
Resource Identifier (URI): Generic Syntax_,
http://tools.ietf.org/html/rfc3986).

Additionally, various other syntaxes and protocols build on that
consistently (e.g., since URIs can never contain space characters,
HTTP uses space characters as delimiters around URI references).


Unfortunately, on the other hand, Unix filenames have no
corresponding specification, at least one that is followed
consistently.  The kernel and file systems allow spaces, and
some utilities/commands/scripts/etc. do, but many don't.



Daniel