[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XSLT vs. CSS (Re: Indexing)

• To: "'Simon St.Laurent'" <simonstl@s...>,'xml-Dev' <xml-dev@l...>
• Subject: RE: XSLT vs. CSS (Re: Indexing)
• From: Didier PH Martin <martind@n...>
• Date: Wed, 09 Jul 2003 11:38:59 -0400
• Importance: Normal
• In-reply-to: <5.2.0.9.2.20030709112002.02404668@s...>

Hi Simon,

Simon said:
And, as noted at the beginning of the conversation, XSLT's lack of a 
cascade means that it too is limited, leaving users at the mercy of the 
choices of the original stylesheet developer when it comes to overriding 
declarations they find inappropriate.

Didier replies:
Totally true. However in recent work I am doing that involves a lot of
usability (After so many years going back to my early Xerox PARC days :-), I
came to the conclusion as Marshall McLuhan came to before me that the
"medium is the message", said differently, the layout also convey some
information like for instance non verbal mimics also convey additional
information to the spoken words. Hence, I am not so sure that the cascading
mechanism which seems practical in theory is that much practical in the real
world. Changing the layout may change some part of the message the author
intended to send. Off course, if the author of the message is taken over by
some convulsive mimics to accompany the spoken words, or that the layout is
as ugly and idiosyncratic as my aunt wallpaper then for sure a cascading
mechanism would find a lot of buyer, but this is a different story :-)

Cheers

• Follow-Ups:
  • RE: XSLT vs. CSS (Re: Indexing)
    • From: Wendell Piez <wapiez@m...>

• References:
  • RE: XSLT vs. CSS (Re: Indexing)
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: RE: XSLT vs. CSS (Re: Indexing)
• Next by Date: Re: Motivations for namespaces (sorry)
• Previous by thread: RE: XSLT vs. CSS (Re: Indexing)
• Next by thread: RE: XSLT vs. CSS (Re: Indexing)
• Index(es):
  • Date
  • Thread