Hi,

> I'm just wondering if anyone here can answer any of them:
>
> 1	Why does XSLT 1.0 have relatively poor string handling
> capabilities?

You mean the lack of a string tokenizer etc.? Probably the WG thought they'd
be an overkill and not needed for XML -> XSL FO conversions.

> 2	When attempting to view an XML document that contains an invalid
> character (for the encoding) in IE it complains that the XML
> document is
> invalid and displays nothing.  However in Firefox the
> document is rendered
> but the character is shown as a black diamond containing a
> question mark.
> Shouldn't Firefox reject the document?

This has nothing to do with XSLT.

Hard to say without seeing the example document and the HTTP headers.

> 3	Where's the documentation for the Transformiix XSLT
> engine that's
> embedded in Firefox?  What extensions are supported? Is it
> scriptable, etc?

<http://www.mozilla.org/projects/xslt/>

Cheers,

Jarno