On Mon, Apr 10, 2006 at 09:15:14AM -0400, Alexander R Pruss wrote: [...] > I was talking of removing pyplucker support, not viewer support. There > is nothing to the viewer support--as far as the viewer is concerned, > these are ordinary hyperlinks. Only until it doesn't try to get the charset metadata for those records. It's simple: the metadata is only assigned to the head record of a sequence, both for continued and linked sequences. Then imagine a reader is processing a request for a record that is in the middle of a sequence of linked records. How does the reader know the charset of that record? To provide such knowledge, the implementation must either track the sequence towards the head (uncompressing records as it goes, etc) at the time of the request, or do almost the same thing, but at opening of the document. Both solutions are ugly and the situation could be much more easy if PyPlucker were attaching the charset metadata for each record that needs one.
_______________________________________________ plucker-dev mailing list [email protected] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
