"Phillip Windell" wrote:
By what means do the contributors contribute? Maybe there
is a way to filter/reject things that aren't formated
properly and distribute instructions for the proper way
to contribute. The problem isn't going to go away if you
don't do something to prevent it.
Who said it was a problem? It bothers me to no extent whatsoever. As I said,
I choose not to police contributors.
The determination that a URL is not well-formed seems to be an arbitrarily
drawn conclusion. Spaces are certainly allowed in quoted attributes, if not
in URLs. But if
http://xx.com/my file.xxx
is an invalid URL and
http://xx.com/my%20file.xxx
is valid, and furthermore
"http://xx.com/my file.xxx"
is a valid HTML attribute value (because it is simple quoted text), should
it not be the responsibility of the browser to apply the proper encoding to
the attribute value when choosing to use it as a URL? The web server, after
all, has the responsibility for the reciprocal mapping to the original
filename (the one with the space included).
FWIW, I note that as I typed this, my NG client identified the quoted
attribute as a URL spanning the space, but not the unquoted example. This
perfectly illustrates my point. Once the text is put into context (in this
case, to be treated as a URL), the client, which happens not to be a
browser, properly encodes the text.
--
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.