Allow negative struct parent keys in PDFMergerUtility#149
Allow negative struct parent keys in PDFMergerUtility#149bernhardf-ro wants to merge 1 commit intoapache:trunkfrom
Conversation
PDFMergerUtility expects structural parent tree keys to be non-negative. However, negative values don't seem to be forbidden by the specification and are accepted by validators. This patch adapts the class to handle negative struct parent keys correctly.
|
Do you have a PDF where this happens? |
|
Here is a document to verify the issue. (Sorry, I forgot to add that to the issue in the first place.) |
| { | ||
| int structParent = annot.getStructParent(); | ||
| if (structParent >= 0) | ||
| int structParent = annot.getCOSObject().getInt(COSName.STRUCT_PARENT, Integer.MIN_VALUE); // allow for negative struct parent values |
There was a problem hiding this comment.
This doesn't change anything but the default value if STRUCT_PARENT is null. If Integer.MIN_VALUE makes more sense than -1 the getter should be changed rather than this piece of code
There was a problem hiding this comment.
I intentionally kept the patch to one class and as simple and minimal as possible, e.g. not renaming variables. So feel free to adapt it and let me know if you have any questions.
There was a problem hiding this comment.
So the question is, do we need to change the default value if the value isn't set?
There was a problem hiding this comment.
That would be an API change which would break all specific (i.e. positiv or negative equals) checks for -1 in all integrations.
If a one-parameter method that defaults to Integer.MIN_VALUE is necessary (IMHO it is not), it would have to be a new one, e.g. getIntSigned(COSName) (and similar for array, possibly for other number types).
The only change in this regard that I consider necessary is improving the API documentation of getInt(COSName) (and similar methods) to clarify that they cannot be used if the result may be negative.
3 participants
PDFMergerUtility expects structural parent tree keys to be non-negative.
However, negative values don't seem to be forbidden by the specification and are accepted by validators.
This patch adapts the class to handle negative struct parent keys correctly.