ezurl not valid xhtml strict 1.1

Saturday 21 May 2005 4:07:36 am

Hi, Xavier.
I might be wrong but I think the & in the URL is valid and should not be encoded.
The XHTML validation problem cannot be located there. I checked and the XHTML standard says that URI are defined by RFC2396 and the RFC says

      reserved    = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" |
                    "$" | ","

The "reserved" syntax class above refers to those characters that are allowed within a URI, but which may not be allowed within a particular component of the generic URI syntax; they are used as delimiters of the components described in Section 3.

Bye

Saturday 21 May 2005 5:06:41 am

Nope, Xavier has right, all "&" characters in URL should be encoded as "&"

http://www.w3.org/TR/xhtml1/#C_12

"C.12. Using Ampersands in Attribute Values (and Elsewhere)

In both SGML and XML, the ampersand character ("&") declares the beginning of an entity reference (e.g., ® for the registered trademark symbol "®"). Unfortunately, many HTML user agents have silently ignored incorrect usage of the ampersand character in HTML documents - treating ampersands that do not look like entity references as literal ampersands. XML-based user agents will not tolerate this incorrect usage, and any document that uses an ampersand incorrectly will not be "valid", and consequently will not conform to this specification. In order to ensure that documents are compatible with historical HTML user agents and XML-based user agents, ampersands used in a document that are to be treated as literal characters must be expressed themselves as an entity reference (e.g. "&"). For example, when the href attribute of the a element refers to a CGI script that takes parameters, it must be expressed as http://my.site.dom/cgi-bin/myscript.pl?class=guest&name=user rather than as http://my.site.dom/cgi-bin/myscript.pl?class=guest&name=user."

Saturday 21 May 2005 8:11:36 am

Thanks Marek and Liu, I was feeling a little bit lonely on that one ;)

Actually, that's mister validator.w3.org that told me it isn't valid.

About liu patch :
http://ez.no/community/bugs/ezurl_does_not_generate_valid_xhtml_1_0_for_external_link

I guess the argument saying it shouldn't be inside of ezurl but an operator is logical.

Liu, have you done it like that or did you keep the modified ezurl ?

X+

http://www.sydesy.com