> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Bryce Yancey
> Sent: Saturday, August 07, 2004 11:09 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Critical problem in new format (was: Support for new
> Plucker features in the Par
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 navig
>
> 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
On Sat, Aug 07, 2004, David A. Desrosiers wrote:
> Would it be possible to make the viewer do this automagically, upon
> opening an "older" format document?
Wrong direction ;-)
The problem with a non-backwards compatible change to the Plucker
format is that only new viewers would be able
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.
Would it be possible to make the viewer do this automagically, upon
opening an "older" format document? The problem I see with writing a script
to
On Sat, Jul 03, 2004, Bryce Yancey wrote:
> The latest revision of the Plucker Document Format
> (http://cvs.plkr.org/index.cgi/docs/DBFormat.html) adds support for
> several new features that require parser support to completely
> implement. Now that the latest revision of the Plucker document fo
