Hello Mathias
On 17-Jul-01, you wrote:
>
> Hi!
>
> How come Voyager wont work with YaBB boards? If I look at the source I find
> the following link:
>
> YaBB.pl?board=general&action=display&num=994667449
>
> But if I check which link Voyager tries to get to (i.e. when I click the
> link or choose to copy URL) it's:
>
> YaBB.pl?board=general&action=display#=994667449
>
> Looks to me (not being a HTML expert) that &num is a reserved word for the #
> symbol, but should Voyager really replace it when it's within "" signs like
> with a link? Sounds like a bug to me...
No, it's not a bug. If you put an entity in the URL like that then it will be
converted by useragents with slightly more slack parsers: that would be
Netscape and IE4.x and all the rest - including Voyager.
# is some HTML entity definition for #
The reason it doesn't do this in IE is because # doesn't work in IE - it's
not an entity that it recognises. We had this exact problem on www.aros.org
where they had a counter image that used the url "blah.pl?blah=10&comma=no"
where V would convert &comma into ',' - this is perfectly valid behaviour, and
the ONLY solution is to get rid of # as a valid entity.
Consider that done.
> Or maybe it's not HTML4 compliant to use &num in a link like that? If that's
> the case I guess I need to ask the YaBB authors to change it, or do it
> myself...
It's NOT strictly HTML compliant to use &num like that: they make
recommendations to use another character (I don't recall which, I think it
was semicolon) to seperate variables in a uri, so you'd never get that
problem. Unfortunately absolutely f**k all of the webservers and scripting
languages actually support this encoding method.
Thanks
--
Matt <[EMAIL PROTECTED]>
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
