--- Comment #6 from Andreas L. Delmelle <> 2011-04-16 
14:35:44 EDT ---
(In reply to comment #5)
> Well, I guess that would depend on how this was implemented. If we were being
> puritanical, one could argue that if FOText was an object representation of
> #PCDATA (which I'm pretty sure it is), then by creating a #PCDATA child in the
> FOTree, we are creating an invalid node. 

No, we're not. #PCDATA is always a valid child node for a marker (i.e. the
content model for a marker is "(#PCDATA|%inline;|%block;)*"). 
It will only, potentially, /become/ invalid in the retrieval context.

In the same sense, one could reason that the marker's child blocks, tables,
lists etc. all should not be created, and we should store the FO source rather
than parsing them into FONodes.
There might be good points for, but also against.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to