RE: lynx-dev Conversion of special character codes within anchor tags

[Leonid Pauzner]

>      * From: Dave Eaton <address@hidden>

> My reading of the W3C's definition of URI syntax
>     http://www.w3.org/Addressing/URL/uri-spec.html
> and the URL spec
>     http://www.w3.org/Addressing/URL/url-spec.html
> seems to put "&" in the "safe" category ... and does not mention character
> entities, but does say "Spaces and control characters in URLs must be
> escaped for transmission in HTTP, as must other disallowed characters."
> The spec defines "escape" as "% hex hex".

This are a different subjects: URL/URI in HTTP transmission
and HREF='...' in HTML which may be encoding as other HTML entries
(I do not like this either but just explain AS IS).

> It appears to me Bruno's point that Lynx should not try to interpret the
> "&" as special is the correct position and that Lynx's code should be
> looked at again.

>  Dave Eaton
> --
>  Artronic Development  - Your Web Site Solution
>  12629 N. Tatum Blvd., Suite 224; Phoenix, AZ 85032
>  e-mail: address@hidden - voice: (602) 953-0336  -  http://www.arde.com
>      _________________________________________________________________

>    References:
>      * RE: lynx-dev Conversion of special character codes within anchor
>        tags

>      * From: "Bruno Prior" <address@hidden>
>      _________________________________________________________________

>      * Prev: Re: lynx-dev Conversion of special character codes within
>      * Next: Re: lynx-dev Conversion of special character codes within
>        anchor tags
>      * Index(es):
>           + Main
>           + Thread
>      _________________________________________________________________

>    Lynx mailing list archives

>    [FLORA HOME] [LYNX Home]