My xsl is a style sheet as well:

<?xml version="1.0"?>
<!DOCTYPE xsl:stylesheet [
<!ENTITY nbsp '&#160;'>
]>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
xmlns:msxsl="urn:schemas-microsoft-com:xslt"
xmlns:fo="http://www.w3.org/1999/XSL/Format"; exclude-result-prefixes="fo">

As for the input comment, sorry for not being clearer about this. Basically
the java program I am working with has a method to process an XSL file (the
same one I am declaring the entity in above). It returns a string containing
all the output from the XSL. It is this string that I am using to create my
input source for FOP. At present FOP is throwing exceptions because of bad
html or undeclared entities. As it turns out &nbsp was not the only concern.
The string I receive back also contains div tags which are missing the
quotes around the names of style classes they are applying. I was thinking
tidy would be the best way to resolve these issues once and for all.

Thanks,

Luke

----- Original Message ----- 
From: "J.Pietschmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 12, 2005 4:57 PM
Subject: Re: Declaring an entity for FOP to see


> Luke Shannon wrote:
> > org.apache.fop.apps.FOPException: The entity "nbsp" was referenced, but
not
> > declared
> >
> > The strange thing is I have this tag at the start of the xml document
that
> > supplies the input to FOP:
> >
> > <?xml version="1.0"?>
> > <!DOCTYPE xsl:stylesheet [
> > <!ENTITY nbsp '&#160;'>
> > ]>
>
> If this is a the beginning of the XML source rather than the style
> sheet, it's of no use (unless your XML source is a style sheet too).
>
> > Should that not handle this? I can see the input being passed still
contains
> > &nbsp, not sure why.
>
> I have no idea what you mean here. What input passed to whom?
>
> J.Pietschmann
>
> ---------------------------------------------------------------------
> 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