Appreciate the comments. I'm going to spend some time on content first, then come back to this.
I'm still not clear on the tables vs. CSS issue. Yes, presentation vs semantics - I grok that. I've read the articles, am familiar with the trend. But we already do this with xdocs.
Are you going to use the Forrest system?
http://forrest.apache.org/0.6/index.html
I think you get all this for free and some apache projects are already using it.
As to not being clear on the tables v. CSS issue, the main problem is that you won't be able to display the 100% Buzzword Compliant [TM] gif :)
Seriously, using a print.css is very nice. And having the (X)HTML as basic as possible, generated by XSL/DVSL, and styled by CSS makes for a very flexible website.
best, -Rob
CSS makes sense to me in some ways. I use CSS extensively in my websites to centralize formatting statements. The printing argument is particularly convincing. (it'd be nice to eliminate the ant task for creating printable documents). I just don't get why everyone is moving from tables to CSS for broad page layout - it seems about the same amount of work. (maybe more- CSS can be quirky with cross-browser issues and has trouble with footers).
Best, WILL
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
