Re: tables/css/screen readers

This is the whole point...we (Designers) have, over time, forced tables to
jump through hoops they weren't intended to ever manage just because the
people with the money wanted something HTML could not deliver.  That just
means the language's development is market-driven, which isn't a bad
thing...I might guess it's how most of human development has been driven.

Of course we are moving toward better...CSS positioning IS better...it
rivals the non-table tools available to the print industry (The printed
Yellow Pages doesn't use tables...they just put things on paper where they
want them!)  Of course this brings special issues in an industry where
delivery isn't related to visual display surfaces such as those print deals
with.  So, rather than make several copies of the data, why not separate the
data from the presentation and mark it up as appropriate for a cell phone or
a browser?

The concepts are great, and the implementation is evolving fairly quickly,
considering only a few years have gone by since the projects were started.
If it takes another 5 years for the older browsers to dissappear, that will
still be an amazingly quick evolution for such a large audience.

Anyway, ideally we should be able to deliver in 3.2 for 4.x and older, XHTML
for 5.x and newer, and other formats as needed, all from 1 web page.

Oh...that's right...we can do that now with PHP...:)

D



----- Original Message -----
From: "Bert Doorn" <bert(at)betterwebdesign.com.au>

....

Should work in any browser!   Your clients will love you for it, even if
people don't buy their products because the site is more boring than a
telephone book.  You might not get paid much for it either.  Hmm.  Talking
about telephone books, our Yellow Pages (printed) does have images.  And
they are positioning the images in a table. Vandals!

My own (poor) attempt at Fuzzy logiic.

....

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA