Andreas L Delmelle wrote:
> On Mar 6, 2006, at 01:25, Florent Georges wrote:
> > Andreas L Delmelle wrote:
> >> The problem is an empty fo:instream-foreign-object.
> > Thanks for the solution (mmh, this file passed my
> > validator, I'll have to check that).
> Well, AFAICT, it's not really empty from a SAX parser's
> point of view. It does contain a text-node, but this is
> completely ignored by FOP. The SAX characters() events are
> only handled for FOs that can contain #PCDATA.
Mmh, I'm not sure to understand. The document contains
some:
<fo:instream-foreign-object/>
as well as some:
<fo:instream-foreign-object>...</fo:instream-foreign-object>
I guess you only saw the later. Furthemore, if I
understand right §6.6.6 (mmh, ok, born to be a problematic
paragraph :-p):
Contents:
The fo:instream-foreign-object flow object has a child
from a non-XSL namespace. The permitted structure of
this child is that defined for that namespace.
So it is required to an IFO to have a child element, isn't
it? And to don't have non-whitespace #PCDATA. Right? So
an FO validator would have to report an error for both the
above IFOs, isn't it?
PS: I based my validator on the RNC grammar provided by
RenderX at <URL:http://www.renderx.com/tools/validators.html>.
Regards,
--drkm
___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
