David Goodger wrote:

> [URIs] If we disallow internal whitespace, rewrapping could cause an
> error.  It's a tradeoff; which is the lesser evil?

I think the combination of

1. long URLs
2. which are split
3. and then (edited and) rewrapped

occurs much more seldom than a user typing whitespace where he should
have typed %20.

So disallowing internal whitespace (while still allowing URLs to split
with newlines) seems like the better choice.

> External hyperlink targets ought to be checked for illegal characters.

Indeed.

And probably non-ASCII characters should be percent-sign-escaped with
UTF-8.  (UTF-8 seems to be the most commonly used encoding [Google,
Wikipedia], and it can encode all Unicode characters.)

>> FYI, Dan wrote (off-list) that MSIE chokes on backslashes combined
>> with %20 in one URI.
>
> Did forward slashes work OK?

Yes, they did.

-- 
For private mail please ensure that the header contains 'Felix Wiemann'.

"the number of contributors [...] is strongly and inversely correlated with the
number of hoops each project makes a contributing user go through."      -- ESR

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click