1

(26 replies, posted in General discussion)

MattF wrote:

Just a quickie. big_smile Has anyone else been having a problem with the W3C validator showing messages/errors that don't appear to make sense?

Lol that really made be laugh a lot.  How many newbies could put there hand up to that?  Thousands would be an understatement. 

Personally I don't see   very usefully at all, and have not used it for ages.    Padding or margin is much quicker to tweak, useing   could mean editing lots of pages if I need to change it later. Which I would because I am never happen with how my site look, I always see a better site and am envious.

If you don't plan to use any of the XML functions you don't need it, I think http://php.net/manual/en/ref.libxml.php would help. 

Michael

Oh and since everything is in XHTML and looks like it is going to stay that way, does any one realize that element names should be in lower case in the CSS if useing it with XHTML?    http://www.w3.org/TR/xhtml1/#C_13  The reason for this is kind of given in http://www.w3.org/TR/xhtml1/#h-4.2

4

(3 replies, posted in PunBB 1.2 discussion)

Because that is the one thing I might find even more annoying...

lol

5

(3 replies, posted in PunBB 1.2 discussion)

I don't like that little page that comes up after you post a new topic, add a reply or change something in the admin panel.  Is there a mod to remove all of them?  I did a search but it did not turn up anything.  I am an new to useing punbb, though it is not bloated like many other forums, I don't like the idea of digging though all the code and working out what needs changing.

Edit:  I worked it out, you set the redirect time to 0.

Firefox has a very nice Vaidator extension that will pick up everything, width very useful error messages too. The link is http://users.skynet.be/mgueury/mozilla/ for those interested.  The errors you get in Opera (and Firefox) when serving the page as XHTML are only the real big bloopers (we all make typos).  So I don't agree with it being easier to validate. 

XHTML strict 1.0 sent as text/html is allowed if I remember right in the standard. XHTML 1.1 sent as text/html is considered wrong.

I think Ian Hickson's opinion does count for something, he is in the credits for helping to writing various parts of the W3C specifications  and also for helping to implement Firefox's rendering of any SGML document.  I think he knows what he is talking about.

And don't get me wrong, I like XHTML and use it when I can't care and iota about IE or older browsers.  Normally when I want to mash it in with other types of XML, that they don't support anyway.  I write my pages so it would be very simple to change to XHTML, I find it easier to come back to pages if I have closed all my <p> and <li> and most of the other stuff. I can't wait till HTML is passed out to either HTML 5 (yes that is on the way too) or XHTML 2.

Well you have half your wish of everything being xml/xslt.  XHTML is XML, even if XHTML 1 is just kind of hacked into working with a XML phaser.  I don't think xslt will become wide spread for styling web pages.  CSS is powerful enough for most people, and xslt is more complicated to write.  I can see myself useing it though, but I am not your average user.  It will take a while till we can, 15 years or so before it is supported by enough user agents and then creeps into the web developers normal tool kit.  Right now I am looking ford to seeing CSS3 working right.

I am not sure yet if I will change the doctype to HTML, I would have to change all the input and img tags.  But there is also the point that most browsers will treat it as HTML, and not only that as some tag soup since it does not have a valid HTML doctype.  Or I could just use a trick in my .htaccess to do content negotiation.