Den 8. aug. 2008 kl. 07.10 skrev David Crossley:
I just checked our sample. No, our packaged Cocoon does not handle that. If we define it that way, then it just includes the whole file.
That is expected behaviour, since the old implementation does not know about the xpointer attribute.
We need to open an issue until it is fixed at Cocoon, and until we use a newer Cocoon. I have not checked the Cocoon-2.2 code. Could someone do that and see if Cocoon have an open issue about that. Should we remove that part of our sample, or add a warning?
I think a warning would be enough.
The DTD changes done in FOR-1032, will later need to be enhanced to handle the "xpointer" attribute.
yes. Sjur
