thanks, also thoughts on xsl:script and xsl:function

Various bits of good advice from (in alphabetical order by last name ;-)
David Carlisle, Peter Flynn, Mike Kay, and Jeni Tennison helped me to
eventually identify the problem:

<!DOCTYPE ROOT [
    <!ENTITY % character_entities SYSTEM "character_entities.dtd">
    %character_entities;
    <!ENTITY events    SYSTEM "events.sgml">

>

It's easy to miss that closing square bracket!  **Argh!**


Re: <xsl:script>, I've done some more thinking about this, and have come
around to the view that having a common binding per language is better
than not having one.  I would prefer not to see other languages inlined
within XSLT source -- I take it that there must be a substantial user
base that needs to have everything packages in one file instead of (for
example) one per language?  Support for an <xsl:binding>, without inline
scripting, is about as far as I have swung so far.


Finally, wouldn't it be useful for <xsl:function> to return multiple
items?  (Though I guess it would have to be called <xsl:relation>
instead! :-)  Sure, it is possible to encapsulate multiple values into a
single one to get around this, just as it is in many other languages,
but why create the need to?

Dave



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