Quote:
Originally Posted by frabjous
I havent conflated them, but how else do you style XHTML (currently)?
|
The fact remains, it's not even XML...
Quote:
|
If I found out that a professional publisher were using MS Word
|
Okay, they're using InDesign then, if you want to use semantics...
Quote:
|
I don't see why we can't expect copy editors and typesetters at presses to know mark-up languages.
|
Same reason it's not expected that anyone who needs to change their graphics drivers would be expected to program C++. There's a good reason people use GUI's for the vast vast majority of their work.
Quote:
|
There's nothing about CSS that prevents providing people a simple quasi-WYSIWYG interface for entering content.
|
Quasi? No, WYSIWYG period. And there were such editors coming along very well before CSS, but they were more or less deliberately killed off in the CSS era because it was near-impossible to manage them.
Forcing people into a few set packages rather than letting them lay out a simple website in a WYSIWYG editor is silly.
It's the same old thing over and over - CSS has amounted to a protectionist manifesto for web designer's jobs, and I'm sick and tired of their defence of it. It's crap, let's replace it with something which can actually be implemented properly, uses XML markup and dosn't cause issues with designing WYSIWYG editors!