Re: Encoding needed for `browse-url' URLs (IDLWAVE html help)

[Kevin Rodgers]

David Reitter wrote:
> I got the below bug report and I found that idlwave does not encode  the
> URL in `idlwave-help-html-link', i.e. if the path contains a  space, it
> is not encoded as "%20".
>
> Are `browse-url'  and the function pointed to in `browse-url-browser-
> function' supposed to handle such URLs or not?
> If not, it's a bug in idlwave-mode (but possibly in other places).

No, browse-url expects a URL that is valid w.r.t. the spec.  That is why
the browse-url-of-file command calls the browse-url-file-url utility to
transform the file name to a valid URL before calling browse-url.
Presumably idlwave should do the same thing.

--
Kevin Rodgers