Am 14.05.2012 10:11, schrieb Maruan Sahyoun:
...
WRT 1.7 I agree with Timo that the enhancements made so far do
validate a new release esp the new NonSequentialParser Timo created
has already proven to solve a number of issues raised. Maybe this
could be the default for the time being?

I wouldn't make it default since it will change which documents can be processed and which throw an exception. While for most documents it should be a big step forward there might be some strange/broken documents for which the standard parser succeeded using workaround and the new one will fail. One possibility would be to write a wrapper (as was proposed in PDFBOX-1199) which first uses the new parser and falls back to the old one in case of an error.

Another issue is that the new parser needs a file as input for random access while the old parser also accepts a stream. This could be tackled by creating a temporary file from stream and use this as input.
I could add this in the next days.

Two further issues:
- need to add method/constructor parameter for specifying password for
  encryption
- signed documents are not tested; I would suppose that the signature
  string will also be decrypted which is wrong as far as I understand
  the spec; there is an implementation for standard parsing
  decryption to prevent this but it relies on all objects already loaded
  and I need another way to detect which strings not to decrypt

Thus in order to release a stable 1.7 in a short time frame I would propose keeping the old parser the default but proposing to use the new parser if possible. If all issues are resolved we may release a 1.8 with the new parser the default.


Best regards,

Timo

--

 Timo Boehme
 OntoChem GmbH
 H.-Damerow-Str. 4
 06120 Halle/Saale
 T: +49 345 4780474
 F: +49 345 4780471
 timo.boe...@ontochem.com

_____________________________________________________________________

 OntoChem GmbH
 Geschäftsführer: Dr. Lutz Weber
 Sitz: Halle / Saale
 Registergericht: Stendal
 Registernummer: HRB 215461
_____________________________________________________________________

Reply via email to