How about fixing the "new format" to be backwards-compatible, instead? I think compatibility of the format extensions are paramount.
Bill > 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. > > 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. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
