On Mar 6, 2006, at 10:05, Florent Georges wrote:
Andreas L Delmelle wrote:
On Mar 6, 2006, at 01:25, Florent Georges wrote:
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):
Yep, my mistake, I only saw the latter. Anyway, what I mean is that
the SAX Parser used with FOP will report those three '.' characters.
That is: any compliant XML parser MUST report those characters to the
application. Only FOP does nothing with them, and those characters
are ignored.
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?
Yes. Exactly one child that is not in the XSL-FO namespace.
And to don't have non-whitespace #PCDATA. Right?
Hmm... Yes, if I catch your intention correctly.
So an FO validator would have to report an error for both the
above IFOs, isn't it?
I'd think so, yes. OTOH, if you have an i-f-o that contains some
text, and then a foreign XML node, I'd assume that a warning would
suffice...
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
