[
https://issues.apache.org/jira/browse/PDFBOX-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444508#comment-17444508
]
Emmeran Seehuber edited comment on PDFBOX-5322 at 11/16/21, 12:33 PM:
----------------------------------------------------------------------
[~mkl] Ok, thats news to me that setting properties is forbidden after defining
a path. Where in the PDF spec (1.7) is this specified? I only found in 8.5.2.1
that after a path construction it "{*}may{*} concluded with the application of
a path-painting operator". As a non native english speaker I assume this means
that a path construction does not require that the path is instantly used.
Never the less I changed in my pdfbox-graphics2d bridge the ordering, so that
after the path construction instant a fill or a stroke is done, and all
properties / graphics states are defined before the path construction is done.
The problem still persists. See [^buggy_shape_operation_order_fixed.pdf]
Is there anything else in the PDF which is broken and could cause that problem?
was (Author: rototor):
[~mkl] Ok, thats news to me that setting properties is forbidden after defining
a path. Where in the PDF spec (1.7) is this specified? I only found in 8.5.2.1
that after a path construction it "{*}may{*} concluded with the application of
a path-painting operator". As a non native english speaker I assume this means
that a path construction does not require that the path is instantly used.
Never the less I changed in my pdfbox-graphics2d bridge the ordering, so that
after the path construction instant a fill oder stroke is done, and all
properties / graphics states are defined before the path construction is done.
The problem still persists. See [^buggy_shape_operation_order_fixed.pdf]
Is there anything else in the PDF which is broken?
> PDFDebugger: Strange zoom depending fill/clipping artefact
> ----------------------------------------------------------
>
> Key: PDFBOX-5322
> URL: https://issues.apache.org/jira/browse/PDFBOX-5322
> Project: PDFBox
> Issue Type: Bug
> Components: Rendering, Swing GUI
> Affects Versions: 2.0.24
> Reporter: Emmeran Seehuber
> Priority: Minor
> Attachments: buggy_shape_operation_order_fixed.pdf,
> image-2021-11-15-19-00-01-859.png, image-2021-11-15-19-00-24-192.png,
> kartenvorschau2871641668946630670.pdf
>
>
> The attached (test) PDF is not rendered correctly in the PDFBox Debugger, at
> least on MacOS with both Azul-17 and Azul-11 JDKs.
> The way it is misrendered is depending on the zoom level. It seems fine at
> 150%, but buggy on all other zoom levels.
> 100%:
> !image-2021-11-15-19-00-01-859.png|width=335,height=184!
> 200%:
> !image-2021-11-15-19-00-24-192.png|width=365,height=195!
>
> It renders fine on Adobe Acrobat and MacOS Preview. (The text is exported as
> vector shapes)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
