At 12:55 AM -0400 4/14/99, Fred Condo wrote:
>I'm the originator of this bug report, and it occurs to me there are two
>separate problems.
Hi! I'm sorry I didn't realize you were on the list.
>Htsearch generates and uses this, so it shouldn't be a big matter to
>change the
>separator. A quick check with the W3C validator shows that encoding the
>ampersands as & validates under HTML 4.0 (strict) and works with Netscape
>4.51.
Hmm. If I understand you, the problem is that & should be used? Are all
browsers going to send the correct & separator to the program?
>CGI scripts, which are I would guess the principal users of the & separator.
>But it's conceivable that there are still URLs that have & in them. I don't
>know that there is any easy answer for this, unless the & solution noted
>above is generally good.
..
At 3:16 AM -0400 4/14/99, Torsten Neuer wrote:
>In fact the specs (6.4) refer to RFCs 1630 (URI) and 1808 (URL).
>AFAIK CGI parameters and their respective separators are part of those.
>IMHO W3C cannot change their meaning unless those RFCs are changed, too.
>Furthermore this would lead to a complete incompatibility in *all*
>CGI applications on the web, which cannot be a task of W3C.
Yeah, I'm not sure & is going to work in all browsers, and the RFCs are
pretty clear on the use of separators. I've also read those RFCs in regard
to encoding and they're not clear on whether an SGML-encoded entity is
legal in a URI. The *correct* URL encoding involves %nnn.
That said, we still have to put SGML entity decoding into our URL code
because some WYSIWYG editors insist on putting them in this way.
-Geoff
P.S. Any comment about "it's conceivable that there are still URLs" isn't
met in reality. IMHO, there will be URLs with & in them for a *long* time
to come. Just like the HTML parser has to deal with non-standard HTML,
we'll have to deal with non-standard behavior.
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
