Just tried, works beautifully:

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output encoding="iso-8859-1" method="text" />

<xsl:variable name="google"
select="document('http://www.google.com/xml?q=libxml')" />


<xsl:template match="/">
Document element: <xsl:value-of select="name($google/*)" />
Results:
<xsl:for-each select="$google//R">
<xsl:value-of select="U" /><xsl:text>&#010;</xsl:text>
</xsl:for-each>

</xsl:template>

</xsl:stylesheet>


> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Syn-Ti Ng
> Sent: Thursday, August 30, 2001 9:54 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  http request - unexpected characters after
> documentend
>
>
> Actually, I've tried several sites; I've tried a transitional
> xhtml and strict xhtml (from  www.w3.org) and I've even tried
> some of my own simple ones on our server. All complain about
> 'line: 2, col 3 as well. The only place I've seen it done is:
>  http://www.dpawson.co.uk/xsl/sect2/N2602.html#d113e348
>  (point 11) but I've found this site to be wrong at times.
>
> Syn-Ti
>
>
> > Anyone know?  - I checked out the spec and I couldn't see anything which
> > explicitly said you could or couldn't do this, nor was their anything I
> > could find in the XSLT books I've got lying around.
>
> Why shouldn't it be allowed? It's useful, it works (if what you
> get is XML),
> and it's not forbidden in the spec.
>
>
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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