[TYPO3-content-rendering] Ampersants in URLs, XHTML-compliancy

[Ernesto Baschny [cron IT]]

Martin Kutschker schrieb am 10.11.2005 23:28:

>> one of the content bugs we are trying to solve for XHTML-compliancy is:
>>
>> http://bugs.typo3.org/view.php?id=772
>>
>> But I don't see the problem yet (see my last comment). Can someone
>> please tell me if I miss something? For me, TYPO3 is already generating
>> all links correctly (with "&" encoded as "& amp;"), this has been this
>> way at least since 3.7.

> I read your comments, and they are interesting. But in real life this
> isn't what happen. TYPO3 site break xhmtl validity because links use &
> and not &. Definitely not in 3.7. But maybe we're not talking about
> typolinks but links in menus etc. In 3.7 I ended up calling stdWrap.hsc
> for menus to be xhtml compliant. *

I have never called hsc for menu links (just for the content itself, so
 that the "&" in the title gets "&" in the output) and have always
gotten compliant output on that part. So maybe you could provide a
working example where this is the case (in 3.8)?

> If your comment tells me anythign than that we have to revalidate the
> patch. I doubt that your conclusion, that everything is fine already, is
> correct.

Surely not everything is fine, but all situations that are being handled
by the patch (which includes MENUs and much more, not just typolinks!)
were fine already.

That's what my "challenge" here to the group was about: to give me a
concrete situation where we end up generating a link without "&" in
the core! I know that many extentions do that, but that's not the issue
here. And also if one creates the A-Tag in the TypoScript "manually", he
should be using &.

Doing a quick search for "href=" in the source of the core shows me that
almost every one go through htmlspecialchars, so at first I fail to see
where this could happen.

Cheers,
Ernesto