> Okay, the problem was simple (as most are when you get right down to it).
> Explorer automatically converts spaces into an %20 character (escapes
them)
> whereas Netscape doesn't and is, thus, confused when it gets some CGI data
> with spaces in it.
Eesh.
>
> There are other ways to solve this (in my humble opinion) deficiency in at
> least early Netscape (4.03 is the latest I have or want<g>, I just use it
to
> make sure stuff works in both flavor browsers). One way is the following
> little REBOL function:
>
> cgi-escape: func [cgi][
> parse cgi [some [to " " (find replace cgi " " "%20")] to end]
> ]
>
> That got my order forms working, but I still need to handle other
characters
> such as '&'.
I going to have to handle special HTML chars soon. I was hoping there was a
Rebol function to do this straight off. That is encode/decode HTML special
chars.
I've not used it, but as it happens I came across it yesterday while reading
my little Javascript pocket reference. Javascript has a "escape" function to
which the book documents it as "Encode a strnig for transmission. Javascript
1.0; ECMA-262; Unicode support in Internet Explorer 4." Also there is
"unescape(s)" Which decodes an escaped string.
Thought I'd pass it on, in case it became of interest to you. Though I'd
use the Rebol approach too since it seems like it would be more reliable.
> Ah, the adventure of it all.
>
> --Ralph Roberts
>
Indeed.
Brett.
