Topic: Validating my pages?? (good laughter) (Page 1 of 1)

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

Yeah, I always thought that XHTML Transitional was a too little too late standard.

HTML 4.0 even in it's badly phrased form is likely to remain supported throughout web browser for many years to come. Not supporting old HTML would render many many documents on the web worthless. I doubt any company designing a product to be competitive would risk anything like that for many many years. Although, maybe HTML will one day go the way of the gopher. Even still there are still gopher archives online. I was browsing through some of them around a friends place about 6/8 months back.

Although I can see the point in following the standards. If we as a whole choose not to follow the stardards then the web browser developers will write them for us. And as history likes to repeate itself we know each developer will write a different standard.

Were finaly starting to leave those entangled highways behind us. If closing my <br>'s is going to bring me closer to that drive along the pleasntly curvy country road then the "/" character is my new best friend.

It's also good practise for XML, as any single elements (is that what their called?) have to be closed the same way you would with XHTML strict (no space, eg <br/> ).

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

But you don't need those closing tags in XHTML. You can use a single tag like <br />. XHTML was only designed so that HTML code was correctly written. It merely requires syntax to be exact. Such things as all tags are lower case, and all values are quoted. All non closing tags have the trailing slash. That's really no biggie. If you write the HTML code correctly to begin with, it's no big deal.

<META NAME=GENERATOR CONTENT=MAX's HTML Beauty++ ME> just gets replaced with
<meta name="generator" content="MAX's HTML Beauty++ ME" />

When you look at it, most of the things required by XHTML were originally required for correct HTML, but people got sloppy and didn't do them. I, for one, have never liked upper case tags anyways.

We'll always have new standards and stuff. This one isn't so bad, so far.....

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

Well, ya know - a good global search/replace feature in your editor is the best way to get started. Replace <br> with <br />, then go after all the unquoted tag values. Then validate. The W3 validator will tell you everything that's wrong with the page, and you can just keep updating till it's compliant.

Oh yeah - change onClick to onclick in any <a> tags that are using that event. That one was killing me.

Ini, I think you may be missing the point of XML. Sure it's not a real language, it's a real mark-up language. You define your language's syntax by means of a Document Type Declaration that let's you parse your data for validity. XML isn't meant to do anything Java and Flash do (well, Java can be used to model data, but it doesn't do it as precisely), it's meant to be a glue layer between various applications.

XML is a subset of SGML that is specifically designed with performance issues in mind. It lets you keep strict control over your data, in a format that is efficiently read and verified. What application does that have for web page design? Well, it does add a lot of work just for data-integrity checking, but suppose you add another application to your data, suddenly you have your data in a format that can be easily translated to multiple applications. Since the DTD defines the format of your data, you don't need to check the validity of your data in every application. The XML parser verifies it, and the various applications just do their thing.

Have you ever noticed how much simpler an SQL database makes developing robust web apps than just using flat files? XML can offer many of the same benefits, but in a general form that is ultimately more flexible.



-jiblet

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

You get to put that ugly arse W3C link button on your site if it validates correctly!

Arrr... Brownie Points?

Maybe just a nice warm and fuzzy feeling. Although, XHTML is meant to be the nail in HTML's coffin. Bye bye HTML. We don't learn or teach you no more cause you suck! Well, you don't but we got someting that makes a little more sence now. Not a whole heap more sence, just a little. So when Billy Bob comes along to fix the company web site after we rip them off for countless millions and skip country he won't be so stumped. You see, poor little Billy only learnt XHTML as HTML was dead or dying when he started in the industry. He sees all of these tags that don't close and arent nested correctly and well.. you get the picture. If we all get used to XHTML with it's lowercase tags and ("") attributes then editing and debugging them becomes a little easier.

If I tried even a lttle bit I'm sure I could have said that in a much simpler way..... eh.

Not really a carrot. More like an lime. It belongs to a family of fruits that one of which is the same colour as a carrot. I guess that's kinda close. Umm.... Donkey want a lime?

Also, I've found practicing XHTML makes my code cleaner and more logocal. Every i dotted, every t crossed. Kinda like going from hand written to typed documents. Try it for a while. If it shits you, don't do it anymore. As you know there aren't really any benifits to XHTML. It's not what id does or how it does it. It's simply a cleaner way to code IMO. However, you may like using the older HTML way better.
Your call.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

InI, read the latest www.alistapart.com article and some of the places it links to.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.