Yes and no. Yes, it repairs Plucker so I can load other documents*, but no, it doesn't allow me to view the actual document in question.
Are you sure the document does not contain corrupted records?
After some digging, I can clearly say: I don't know :)
If I re-convert the file (using jpluck) I get a different binary file each time (must be datestamps or something). But they all crash plucker in one way or another.
*Unless* I rename the document to a short simple name first (it has a 48 character file name with spaces and dashes in it) and then convert, in which case the document loads fine.
But it's not just the file name - if I create another document of similar length with the same (long) file name, it also works fine. As do many other documents with long file names.
Sadly the original document is an internal company document so I can't post it. If I change it in any significant way, such as replacing all text in the document with 'x' characters, the resulting document converts and reads with no problems.
So I have no idea what the problem is, I suspect it is probably JPluck, but can't be sure. Certainly plucker, when it crashes, crashes really impressively - not even CleanPlkr has fixed all my crash problems, renaming the /Palm/Ebook folder has been my only recovery path more than once...
Anyway, when I get a document that exhibits this behaviour that I *can* upload somewhere, I'll do so, and then maybe we can progress further.
- Korny _______________________________________________ plucker-list mailing list [email protected] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
