Re: *input* filters

James,

  I could see a valuable need here, such as converting HTML to
"well-formed HTML" if I wanted to leverage XSL. I could take an HTML
document and convert it into PDF using a "filter" and then using XSL
with a PDF formatter. However some of these tools already exist and
there is nothing stopping people from chaining them together. Is there
an argument that would show the need for this to be included into the
XSL WD?

--Keith

James Tauber wrote:
> 
> It occurred to me the other day:
> 
> Any reason we can't have *input* filters in XSL, ie some specification of a
> conversion to apply to a non-XML files in order to produce the source tree?
> 
> James
> --
> James Tauber / jtauber@xxxxxxxxxxx / www.jtauber.com
> Associate Researcher, Electronic Commerce Network
> Curtin University of Technology, Perth, Western Australia
> 
> Full-day XML Tutorial @ WWW8 : http://www8.org/
> 
> Maintainer of : www.xmlinfo.com,  www.xmlsoftware.com and www.schema.net
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


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