> > I found a critical problem in the new format when working on > the viewer implementation. The problem is that the viewer > will not be able to find the navigation data (put after the > compressed text/image data). One solution would be to add a > new field to the header with the size of the compressed data > or the offset to the navigation data. > > This will, however, make the new format non-backwards compatible.
Bummer. If it's not possible to make these changes completely backward compatible, do we want to consider changing the plucker format version number (currently 2)? That way old readers would presumably report the book as incompatible rather than corrupt...which would be a little less confusing to end users. > > It should be quite simple to write a script that could > convert documents from the new format to the old format > (without the new features), though. Sounds like a reasonable short-term solution. > > It might even be a good idea to add another field that includes the > header size (or offset to the text/image data) to be able to > handle future changes without breaking the format. > Yep. If the format must change, it would be good to add some way to better allow for future changes without breaking the format. > Comments? Suggestions? > > /Mike > > _______________________________________________ > plucker-dev mailing list > [EMAIL PROTECTED] > http://lists.rubberchicken.org/mailman/listinf> o/plucker-dev > > _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
