Dear Richard,

A similar behaviour occoures in FireFox when the XSL stylesheet is in a parent 
folder of the XML file.

<?xml-stylesheet type="text/xsl" href="../../../styles/myStyleSheet.xsl" ?>

I moved the XSL into folder "folder_A" so the line in the XML file changed to

<?xml-stylesheet type="text/xsl" href="myStyleSheet.xsl" ?>

and FireFox was able to visualise the XML with styleing. I had this problem not 
only in Apache, but also local ( file:///C:... )
Maybe this helps a bit.

regards,
Vittorio



>>> Richard Rosenberg <[EMAIL PROTECTED]> schrieb am 03.08.2008 um 02:33
in Nachricht <[EMAIL PROTECTED]>:
> Hello:
> 
> I am having some trouble with client-side transformation using docbook-xsl 
> via  
> debian etch and apache 2.x. It works great with IE7, but firefox 2.x and 3.0 
> 
> both display only the text (stripped of xml tags). Firefox also gives 
> numerous messages about localization issues. I understand this may be a 
> no-go 
> with firefox for at least two reasons:
> 
> 1. A mime-type error when fetching the VERSION file from docbook.xsl - FF 
> complains about a missing file extension (this is supposed to be security?)
> 
> 2. document() function in l10n.xsl, right at the top:
> 
>       <xsl:param name="l10n.xml" select="document('../common/l10n.xml')"/>
>       <xsl:param name="local.l10n.xml" select="document('')"/>
>       ...
> 
> Apparently FF has problems with fetching l10n.xml and this is giving rise to 
> 
> numerous issues. . .
> 
> Problem number 1 seems solvable. 
> 
> My question is this: Is it possible to do client-side transformations using 
> firefox and docbook-xsl at all? Problem number two seems like it may be 
> related to a bug/feature of FF and not solvable, or is related to my apache 
> setup and may require more work to find the problem. Before I proceed any 
> further, it would be great to know if any one has had success doing 
> client-side transformations with firefox and apache.
> 
> Thanks,
> 
> Richard
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to