|
|
Posted by aioe-user on 04/15/07 02:34
Too many years ago to remember I got my first lesson in
creating HTM pages and here's what an entire HTM file
with the letter X then looked like.
«html»«body»X«/body»«/html»
Total size 28 bytes, and if you wanted to format it like
«html»
«body»
X
«/body»
«/html»
then you were definitely a 'bandwidth HOG'.
It was nice, it "was" both lean and (therefore) fast!
An important consideration back when 56k was still
unheard of. As a matter of fact taht hould STILL be an
overriding consideration because according to
http://www.webusability.com/user_profile_stats.htm
1/3 the US is STILL on 56k, and probably 80% of the
world 'net' population will stay on 56k it for decades more.
Today that kind of simplicity would be lightning fast,
maybe even too fast and so most people would add a few
more words and things of that nature.
So lately I decided to show my first ever HTM page to the
W3C facility ...it failed from A to Z so for now I'll
just think of it as a WC facility (between friends as I
well know that there must be standards). Anyway, I next had
the composter "correct" the same page and that version passed
but did so only by becoming a 281 byte file instead of 28
which, unless my math has also been left in the dust, is close
to a *10 FOLD BLOATING COEFFICIENT!*
(the files and reports appended below)
Then it got much worse. Another page flunked because it
was missing 'empties' like alt="" (up another 600 bytes
for a page with 100 of them). This kind of insanity is
like having to paint "not painted" on a car that is not
painted. Sheeee!
Boys & girls, I can well understand that some commercial
and/or cultural imperatives have requirements which the
industry tries to satisfy as best it can. Those with a
need for flaming dildos and singing monkeys on web pages
have rights too. But dammit, did you have to kill the
purtity of the original as a timeles option?
Has someone forgot that HTM is still as much a transport
language as US-ASCII is? Who the hell wants more bandwidth
if it will be gobbled up the next day?
Go ahead and do all the MM and all the style sheets you want
but don't muck with basic HTM's sanctity. I want my FAST
pages to pass every test ..if they cannot BE the test itself.
KISS, KISS, KISS. Remember that the Amiga could fly with
no fans and no hard drive and that today's leading 0-noise
projects are aiming to return to that ideal :-)
Cheers.
= Done with Seamonkey Composter ==================
= 10 times the size with a 1,500 byte error report
«!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"»
«html»
«head»
«meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"»
«title»
«/title»
«/head»
«body alink="#33cc00" bgcolor="#ffffff" link="#0000ff" text="#000000"
vlink="#ff0000"»
X
«/body»
«/html»
....
The document ..was checked and found to be valid HTML 4.01
Transitional. This means that the resource in question identified
itself as "HTML 4.01 Transitional" and that we successfully performed
a formal validation using an SGML or XML Parser (depending on the
markup language used).
Valid HTML 4.01 Transitional To show your readers that you have taken
the care to create an interoperable Web page, you may display this
icon on any page that validates. Here is the HTML you could use to add
this icon to your Web page:
«p»
«a href="http://validator.w3.org/check?uri=referer"»«img
src="http://www.w3.org/Icons/valid-html401"
alt="Valid HTML 4.01 Transitional" height="31" width="88"»«/a»
«/p»
If you like, you can download a copy of this image (in PNG or GIF
format) to keep in your local web directory, and change the HTML
fragment above to reference your local image rather than the one on
this server.
A full list of icons, with links to alternate formats and colors, is
also available.
If you use CSS in your document, you should also check it for validity
using the W3C CSS Validation Service.
If you would like to create a link to this page (i.e., this validation
result) to make it easier to revalidate this page in the future or to
allow others to validate your page...
===========================================================
= Done with nedit ================================
= 28 byte file & a 3,200 byte error report =======
«html»«body»X«/body»«/html»
....
No Character Encoding Found! Falling back to UTF-8.
I was not able to extract a character encoding labeling from any
of the valid sources for such information. Without encoding
information it is impossible to reliably validate the document. I'm
falling back to the "UTF-8" encoding and will attempt to perform the
validation, but this is likely to fail for all non-trivial documents.
Read the FAQ entry on character encoding for more details and
pointers on how to fix this problem with your document.
No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.
The DOCTYPE Declaration was not recognized or is missing. This
probably means that the Formal Public Identifier contains a spelling
error, or that the Declaration is not using correct syntax. Validation
has been performed using a default "fallback" Document Type Definition
that closely resembles "HTML 4.01 Transitional", but the document will
not be Valid until you have corrected this problem with the DOCTYPE
Declaration.
Learn how to add a doctype to your document from our FAQ.
This page is not Valid (no Doctype found)!
Below are the results of attempting to parse this document with an
SGML parser.
1. Error Line 1 column 0: no document type declaration; implying
"«!DOCTYPE HTML SYSTEM»".
«html»«body»X«/body»«/html»
The checked page did not contain a document type ("DOCTYPE")
declaration. The Validator has tried to validate with a fallback DTD,
but this is quite likely to be incorrect and will generate a large
number of incorrect error messages. It is highly recommended that you
insert the proper DOCTYPE declaration in your document -- instructions
for doing this are given above -- and it is necessary to have this
declaration before the page can be declared to be valid.
?
2. Error Line 1 column 11: document type does not allow element
"BODY" here.
«html»«body»X«/body»«/html»
The element named above was found in a context where it is not
allowed. This could mean that you have incorrectly nested elements --
such as a "style" element in the "body" section instead of inside
"head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in
HTML documents. Due to HTML's rules of implicitly closed elements,
this error can create cascading effects. For instance, using XHTML's
"self-closing" tags for "meta" and "link" in the "head" section of a
HTML document may cause the parser to infer the end of the "head"
section and the beginning of the "body" section (where "link" and
"meta" are not allowed; hence the reported error).
?
3. Error Line 1 column 26: end tag for "HTML" which is not finished.
«html»«body»X«/body»«/html»
Most likely, You nested tags and closed them in the wrong order.
For example «p»«em»...«/p» is not acceptable, as «em» must be closed
before «p». Acceptable nesting is: «p»«em»...«/em»«/p»
Another possibility is that you used an element which requires a
child element that you did not include. Hence the parent element is
"not finished", not complete. For instance, «head» generally requires
a «title», lists (ul, ol, dl) require list items (li, or dt, dd), and
so on.
======================= END ===============================
Navigation:
[Reply to this message]
|