RE: [xsl] tag minimisation

["Andrew Welch" <awelch at piper-group dot com>]

DC:
> I fail to see why it is a problem at all,

I add custom elements to the output based on the transform that is being
performed at the time.  The app then post processes (sax parses) the
output to extract the info Ive added to populate some of the features of
the app.  As I need xml (xhtml) output, the html output will not do.  

So far so good, and everything works fine.   

The *only* problem comes from the browser (IE - no choice) failing to
recognise <xxx/>.  Any expressions performed on a minimised element will
crash IE, any styling given to a minimised element will be passed onto
all elements that follow it.

On large output files it can be a nightmare trying to locate which
element has been minimised, then tracing it to the template that
generated it and adding #160, purely to stop it getting minimised (which
just seems rediculous).

Its such a trivial, non essential thing that can cause so many problems,
I fail to see why it is a problem to keep elements as <xx> </xx>, at
least until browsers catch up.

MK:
>If you want XHTML, several processors including saxon have an output
>method for XHTML that won't do tag minimisation except for elements
>whose content model is EMPTY.    

That should hopefully do what I need.

cheers
andrew

> -----Original Message-----
> From: David Carlisle [mailto:davidc@nag.co.uk]
> Sent: 10 September 2002 18:55
> To: xsl-list@lists.mulberrytech.com
> Subject: Re: [xsl] tag minimisation
> 
> 
> 
> > Its such a small issue that causes huge problems, I can't see any
> > benefit whatsoever of enforcing minimisation at this time.
> 
> would you object to <hr/> being output as <hr></hr> (and 
> similarly img,
> br, meta, etc?
> 
> I fail to see why it is a problem at all, if you give the file
> containing <div/> to an xhtml renderer such as mozilla or netscape, it
> works fine. If you want to use an html system then quite a 
> lot of things
> are likely to go wrong if you give it xml, so why not use the html
> output method?
> 
> It isn't only <div/> If you are sending to a legacy html 
> browser you'll
> need <br /> not <br/> or <br></br> the content of script elements is
> almost impossible to get right as html script is CDATA and 
> that does not
> exist as an element type in XML, ...
> 
> 
> David
> 
> 
> _____________________________________________________________________
> This message has been checked for all known viruses by Star Internet
> delivered through the MessageLabs Virus Scanning Service. For further
> information visit http://www.star.net.uk/stats.asp or 
> alternatively call
> Star Internet for details on the Virus Scanning Service.
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 
> 
> 
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.385 / Virus Database: 217 - Release Date: 04/09/2002
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.385 / Virus Database: 217 - Release Date: 04/09/2002
 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list