xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henning von Bargen <H.vonBar...@triestram-partner.de>
Subject AW: AW: [OT] Design Rant
Date Fri, 21 Dec 2001 15:13:43 GMT
Ok, let's stop that discussion now, it's gone a bit off topic.
Back to the original question, I think to demonstrate the power of Cocoon,
it should easily be possible to create different versions of the pages:
- one with tables, images, flash and whatsoever
- and a more simple one containing only text with a little CSS.
But each version could contain a link to the other one.
And everybody will feel a little better.
For now, I wish you all a merry christmas and a happy new year!

> -----Urspr√ľngliche Nachricht-----
> Von:	Stefano Mazzocchi [SMTP:stefano@apache.org]
> Gesendet am:	Freitag, 21. Dezember 2001 14:46
> An:	general@xml.apache.org
> Betreff:	Re: AW: [OT] Design Rant
> 
> Henning von Bargen wrote:
> 
> > A HTML page should simply be coded in a linear fashion
> > (I read that somewhere in an article about designing web pages for
impaired
> > readers), so that it is usable with screen readers.
> 
> Oh, please, let's avoid the 'one-size fits all' syndrome that seems to
> hit every W3C WG after a few years: the web architecture has the ability
> to syndicate content, that means that you should ask for the content
> that suits your needs the best. That's the way to go.
> 
> Sure, you can use CSS print media or aural media, but how that compares
> to ad-hoc solutions like XSL:FO and VoiceXML? IMHO, poorly.
> 
> > As a rule of thumb, it should be more or less possible to read the html
code
> > like a book if you think all the html tags stripped off.
> >
> > Tables should be used for tabular data only inside the content
> > and (as a practical exception) can be used inside toolbars at the top
and
> > bottom which aren't part of the content.
> 
> I have an exercise for you: try to apply these design principles to your
> favorite newspaper (the paper version, I mean)
> 
> Now answer this question: what is more economically feasible: selling
> the newspaper as a 200 pages (one size fits all) A4-sized book written
> because the ocr->speech software for visually impaired people are easier
> to write, or adopting a publishing system that is able to present the
> newspaper content (the value-add) in a format that suites people needs?
> 
> Sure, the first solution is much easier for the publisher since it
> doesn't have to have different 'output' channels and manage all of them
> at the same time, but it's a much more realistic approach to publishing
> problems.
> 
> The technology of the press created the same kind of problems that we
> are facing today almost 400 years ago.
> 
> People, wake up! Don't think printed pages are obsolete just because
> they are 'fixed' or because your screen doesn't yet weight 2 grams,
> doesn't bend and doesn't have 2500 Dpi!
> 
> We must go back and learn from the history of printed publishing:
> moveable char sets are the equivalent of stylesheets. Non-book layouts
> (newspaper) were an entirely new way of presenting information (just
> like portals).
> 
> The best web content management and publishing system will be the one
> that will be used for *both* the 'paper' version and the on-line version
> of a newspaper. 
> 
> Until that happens, we have still a long way to go.
> 
> -- 
> Stefano Mazzocchi      One must still have chaos in oneself to be
>                           able to give birth to a dancing star.
> <stefano@apache.org>                             Friedrich Nietzsche
> --------------------------------------------------------------------
> 
> 
> 
> ---------------------------------------------------------------------
> In case of troubles, e-mail:     webmaster@xml.apache.org
> To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Mime
View raw message