Hmm... I need to find out myself. I don't know what is the right answer to your question. I'll do some poking around and get back to you if I bump into an useful answer. You should email the people at iPage as they probably know..
I have a couple uf URL's with ampersands in them and I'm getting an error on validation. Is it anything to worry about?..
Alot of the errors seem small, like having no ALT= but it has a purpose for people with that disability, here's a link to try to validate your code, just erase whats in the box and have your coding copied and paste it in the box. See what it comes up with..
I got it down to where the ampersands are causing the only errors for 4.01 transitional. W3C suggests using '&' instead so Netscape 3 users will see it ok..
I tried the CSS validator for fun and it says.
"To work as intended, your CSS style sheet needs a correct document parse tree. This means you should use valid HTML".
Plus alot of stuff that looks like I'll be busy figuring it out, things like parsing and context errors, although, if I'm looking at what I'm expecting to look at (and wanted to look at), should I bother?.
You may also want to use another validator :.
For the ampersand, you can use the "escape" to make it appear on the web page and have it validate OK too..
& a m p ;.
(take out the spaces)..
...is in the address (ie. I cut and paste the www address from the address bar.) I don't think that the anchor would be a valid url then...
Ah, OK, for an ampersand in a URL, use the ASCII version of it..
For your doctype, this is the one I prefer. N6 seems to like it best as well..
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN".
A bit of an update....
I just validated a page and it seemed to work....
In an HREF value, ampersands are allowed. Otherwise I would go with the %26 thing..
In an SRC value, & a m p ; are allowed and seem to work..
Hope that works for you to. Cheers!..
I've just found out that '%26' doesn't work for XHTML 1.0 Strict, you must use '&'..
I've one more quirky thing about this. The validator says:.
... c=ll&objtype=141&objaction=browse" target="_blank"> LiveLink < ....