list4xt : Mailing list for the XT users community.

[list4xt] Re: XHTML output handler nits

New Message
• Reply
• Next message: Mike Brown: "[list4xt] Re: XHTML output handler nits"
• Previous message: Eric van der Vlist: "[list4xt] Re: XHTML output handler nits"
• In reply to: Eric van der Vlist: "[list4xt] Re: XHTML output handler nits"
• Next in thread: Eric van der Vlist: "[list4xt] Re: XHTML output handler nits"
• Reply: Simon St.Laurent: "[list4xt] Re: XHTML output handler nits"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

At 11:53 PM 5/1/00 +0200, Eric van der Vlist wrote:
>Yes, it's obvious that the nightmare of handling both different releases
>of (X)HTML and also probably vendor differences is going to last for a
>while.
>
>Is there anything else than the C.2 and C.3 appendixes to implement ?
>
>I am also wondering if it wouldn't help to implement an "adaptable"
>output handler which accommodate some of the differences between
>browsers releases.

Well, thanks for ignoring my severe grouchiness of a few hours ago.
Working with XHTML in an HTML environment for a few months can do that to
you... and I have to admit I'm pretty afraid of XHTML 1.1's entering the
picture.

Yes, an adaptable output handler would be nice - if there's a way to pass
it information. I'm not sure XT provides any such mechanism.

>There are many techniques to select a different XSLT transformation
>according to the browser identified by the HTTP header, but it means
>that you have to maintain a set of transformations.

Yes. It might be possible to abstract those sets out a bit, but to a
significant extent it might well involve multiple style sheets, which is
painful. (IE 4.x and previous/Mac's habit of displaying the XML
declaration is a serious hassle, but there's much worse in the 3.x
generation of all browsers.)

>If you could generate a generic XHTML within your XSLT transformation
>and let the output handler adjust to some of the more recent browsers
>(TBD), it could be great.

That'd be nice.

>I know that most of the nasty incompatibilities are with Javascript and
>CSS, but still, isn't it an idea to investigate ?

Certainly - though it might mean building a more comprehensive servlet
framework for XT, or modifying Cocoon perhaps - rather than just more work
on the output handlers.

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
Building XML Applications
Inside XML DTDs: Scientific and Technical
Cookies / Sharing Bandwidth
http://crescentprocessing.com

--
Mailing list for the XT users community.     (http://premierbanknc.com)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)

• Next message: Mike Brown: "[list4xt] Re: XHTML output handler nits"
• Previous message: Eric van der Vlist: "[list4xt] Re: XHTML output handler nits"
• In reply to: Eric van der Vlist: "[list4xt] Re: XHTML output handler nits"
• Next in thread: Eric van der Vlist: "[list4xt] Re: XHTML output handler nits"
• Reply: Simon St.Laurent: "[list4xt] Re: XHTML output handler nits"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]