[
https://issues.apache.org/jira/browse/PDFBOX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr closed PDFBOX-5120.
---
Resolution: Not A Bug
> Need to do strange stuff to create my own PageDrawer Paramet
[
https://issues.apache.org/jira/browse/PDFBOX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr reopened PDFBOX-5120:
-
> Need to do strange stuff to create my own PageDrawer Paramet
ate my own PageDrawer Parameters
> ---
>
> Key: PDFBOX-5120
> URL: https://issues.apache.org/jira/browse/PDFBOX-5120
> Project: PDFBox
> Issue Type: Bug
>
PDFRenderer.renderPageToGraphics would allow me
everything I need. I will investigate this first, thanks.
> Need to do strange stuff to create my own PageDrawer Parameters
> ---
>
> Key: PDFBOX-5120
> URL: https://is
need them to create the PageDrawer:
// the end-user may provide a custom PageDrawer
PageDrawerParameters parameters = createPageDrawerParameters(page);
PageDrawer drawer = new PageDrawer(parameters);
drawer.drawPage(g, page.getCropBox());
Maybe I abused this a bit
[
https://issues.apache.org/jira/browse/PDFBOX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297142#comment-17297142
]
Daniel Migowski commented on PDFBOX-5120:
-
I need them to create the PageDrawer
? There is a method
{{setRenderingHints()}}.
> Need to do strange stuff to create my own PageDrawer Parameters
> ---
>
> Key: PDFBOX-5120
> URL: https://issues.apache.org/jira/bro
:
--
Is this all about passing your own rendering hints? There is a method
{{PDFRenderer.setRenderingHints()}}.
was (Author: tilman):
Is this all about passing your own rendering hints? There is a method
{{setRenderingHints()}}.
> Need to do strange stuff to create my own PageDrawer Paramet
[
https://issues.apache.org/jira/browse/PDFBOX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Migowski updated PDFBOX-5120:
Description:
Currently using the following function to create my PageDrawer Parameters
Daniel Migowski created PDFBOX-5120:
---
Summary: Need to do strange stuff to create my own PageDrawer
Parameters
Key: PDFBOX-5120
URL: https://issues.apache.org/jira/browse/PDFBOX-5120
Project
uld the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
for the spelling mistake :)) to 0: disabling
the optimization altogether.
This is a nice simple fix and exactly what I needed!
Thank you very much!
> Could the new rendering method of PageDrawer be optional?
> -
>
>
with a snapshot:
https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox-app/2.0.22-SNAPSHOT/
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
>
Tilman Hausherr in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1884244 ]
PDFBOX-4928: fix typo
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
>
Tilman Hausherr in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1884245 ]
PDFBOX-4928: fix typo
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
>
shold"
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
Tilman Hausherr in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1884241 ]
PDFBOX-4928: revert accidental change
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key:
Tilman Hausherr in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1884239 ]
PDFBOX-4928: add fine tuning for quality-optimized downscaling, as suggested by
Christian Appl
> Could the new rendering method of PageDrawer be optio
Tilman Hausherr in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1884240 ]
PDFBOX-4928: add fine tuning for quality-optimized downscaling, as suggested by
Christian Appl
> Could the new rendering method of PageDrawer be optio
uld the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
>
...
{{setDownscalingImageOptimizationThreshhold()}}
{{setQualityImageDownscalingThreshhold()}}
{{setImageOptimizationThreshhold()}}
{{setQualityImageRenderingThreshhold()}}
I can't come up with a short one here either...
> Could the new rendering method of PageDrawer be optio
.
{{setThreshholdForQualityImageDownscaling()}} ?
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
>
hod of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
> Components
ed.
*Edit:* The original heic image can be found at
[https://nokiatech.github.io/heif/examples.html|https://nokiatech.github.io/heif/examples.html]
*Edit:* See [^image-2020-08-03-09-43-37-412.png] for a direct comparison.
*Edit:* I am currently using openjdk11.0.6
ithub.io/heif/examples.html|https://nokiatech.github.io/heif/examples.html]
*Edit:* See [^image-2020-08-03-09-43-37-412.png] for a direct comparison.
> Could the new rendering method of PageDrawer be optional?
> -
>
>
.github.io/heif/examples.html]
*Edit:* See [^image-2020-08-03-09-43-37-412.png] for a direct comparison.
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
Edit:* See [^image-2020-08-03-09-43-37-412.png] for a direct comparison.
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/b
s "better". Therefore I would suggest either being able to disable
the prescaling, or to set the threshold - as you suggested.
*Edit:* The original heic image can be found at
[https://nokiatech.github.io/heif/examples.html]
hod of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
> Components: Renderi
ing method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
>
new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
the prescaling, or to set the threshold - as you suggested.
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/b
s seems to come down to mere personal preference, whether the one or
the other is "better". Therefore I would suggest either being able to disable
the prescaling, or to set the threshold - as you suggested.
> Could the new rendering
[
https://issues.apache.org/jira/browse/PDFBOX-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4928:
---
Attachment: prescaled.png
> Could the new rendering method of PageDrawer be optio
[
https://issues.apache.org/jira/browse/PDFBOX-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4928:
---
Attachment: unprescaled.png
> Could the new rendering method of PageDrawer be optio
[
https://issues.apache.org/jira/browse/PDFBOX-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4928:
---
Attachment: (was: prescaled.png)
> Could the new rendering method of PageDra
[
https://issues.apache.org/jira/browse/PDFBOX-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4928:
---
Attachment: (was: unprescaled.png)
> Could the new rendering method of PageDra
[
https://issues.apache.org/jira/browse/PDFBOX-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4928:
---
Attachment: (was: prescaled.png)
> Could the new rendering method of PageDra
hod of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
> Components
hod of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
> Components
[
https://issues.apache.org/jira/browse/PDFBOX-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4928:
---
Attachment: prescaled.png
> Could the new rendering method of PageDrawer be optio
hod of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
> Issue Type: Wish
> Components: Renderi
are not as good as 2.0.19 ?
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/browse/PDFBOX-4928
> Project: PDFBox
>
some PDFs where the new
results are not as good as 2.0.19 ?
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: https://issues.apache.org/jira/bro
s{color}.getRenderingHint({color:#00}RenderingHints{color}.{color:#871094}KEY_QUALITY_RENDERING_METHOD{color})
This would enable the user to directly select whether graphics.drawImage()
shall apply the transformation matrix, or the introduced prescaling shall be
applied.
olor}.{color:#871094}KEY_QUALITY_RENDERING_METHOD{color})
This would enable the user to directly select whether graphics.drawImage()
shall apply the transformation matrix, or the introduced prescaling shall be
applied. (to intentionally enable or disable the prescaling.)
> Could the new rendering me
(default to this: (scaleX < 0.5 || {color:#00}scaleY
{color}< 0.5))
VALUE_NEVER_PRESCALE
The names are not perfect - but this is how I would imagine a parameter like
that.)
> Could the new rendering method of PageDrawer be
... forget about that.
Back to the start:
Could a method be introduced for the PDFRenderer, that would allow setting an
option like that?
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key:
VALUE_AUTO_PRESCALE (default to this: (scaleX < 0.5 || {color:#00}scaleY
{color}< 0.5))
VALUE_NEVER_PRESCALE
The names are not perfect - but this is how I would imagine a parameter like
that.
> Could the new rendering method of PageDrawer be
x, or the introduced prescaling shall be
applied. (to intentionally enable or disable the prescaling.)
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
> URL: ht
shall apply the transformation matrix, or the introduced prescaling shall be
applied. (to intentionally enable or disable the prescaling.)
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFB
this is what you'd want?
Yes, the 0.5 has been set arbitrarily, i.e. by looking at the rendering of the
test images.
> Could the new rendering method of PageDrawer be optional?
> -
>
> Key: PDFBOX-4928
>
-4886, PDFBOX-4863{color}{color:#008dde}
I have tested the new prescaled rendering method for the
{color}org.apache.pdfbox.rendering.{color:#008dde}PageDrawer
{color:#172b4d}with PDFBox:2.0.21-SNAPSHOT{color}{color} for different images,
with different resolutions, target image sizes etc
Christian Appl created PDFBOX-4928:
--
Summary: Could the new rendering method of PageDrawer be optional?
Key: PDFBOX-4928
URL: https://issues.apache.org/jira/browse/PDFBOX-4928
Project: PDFBox
settings. Re "are no
longer rendered" they were rendered until 2.0.15, but rotated. This is weird
because in PDFBOX-4447 where the NoRotate code was created, I had created a
test PDF to verify that it works.
> PageDrawer is not rendering unrotatable Annotations on
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr updated PDFBOX-4744:
Labels: Annotations PDFBox PageDrawer (was: PDFBox PageDrawer)
> PageDra
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4744:
---
Description:
Unrotatable Annotations are no longer rendered by the PageDrawer.
The issue
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4744:
---
Labels: PDFBox PageDrawer (was: PageDrawer pdfbox,)
> PageDrawer is not render
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4744:
---
Attachment: screenshot-1.png
> PageDrawer is not rendering unrotatable Annotati
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4744:
---
Labels: PageDrawer pdfbox, (was: )
> PageDrawer is not rendering unrotatable Annotati
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4744:
---
Description:
Unrotatable Annotations are no longer rendered by the PageDrawer.
The issue
[
https://issues.apache.org/jira/browse/PDFBOX-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Appl updated PDFBOX-4744:
---
Description:
Unrotatable Annotations are no longer rendered by the PageDrawer.
The issue
Christian Appl created PDFBOX-4744:
--
Summary: PageDrawer is not rendering unrotatable Annotations on
rotated pages
Key: PDFBOX-4744
URL: https://issues.apache.org/jira/browse/PDFBOX-4744
Project
handling for Ink and Link annotation.
> Update PageDrawer to match appearance handling in trunk
> ---
>
> Key: PDFBOX-4576
> URL: https://issues.apache.org/jira/browse/PDFBOX-4576
>
Maruan Sahyoun in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1861488 ]
PDFBOX-4576: remove legacy code for Ink and Link annotation now handled by
appearance generation
> Update PageDrawer to match appearance handling in tr
Maruan Sahyoun in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1861487 ]
PDFBOX-4576: support rotation for annotations
> Update PageDrawer to match appearance handling in trunk
> ---
>
> Key:
Maruan Sahyoun created PDFBOX-4576:
--
Summary: Update PageDrawer to match appearance handling in trunk
Key: PDFBOX-4576
URL: https://issues.apache.org/jira/browse/PDFBOX-4576
Project: PDFBox
and causing blank output, I
haven't looked into why yet
> Allow flexible calling of PageDrawer
>
>
> Key: PDFBOX-3100
> URL: https://issues.apache.org/jira/browse/PDFBOX-3100
> Project: PDFBox
>
graphics.clearRect(0, 0, width,
height); is not called by PDFRenderer
> Allow flexible calling of PageDrawer
>
>
> Key: PDFBOX-3100
> URL: https://issues.apache.org/jira/browse/PDFBOX-3100
> Project: PDFBox
>
the crop box
prior to painting. Are we doing this incorrectly? Or is there some other use
case which you're trying to satisfy - if so what?
> Allow flexible calling of PageDrawer
>
>
> Key: PDFBOX-3100
>
[
https://issues.apache.org/jira/browse/PDFBOX-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated PDFBOX-3100:
--
Description:
You used to be able to do:
PageDrawer drawer = new PageDrawer
[
https://issues.apache.org/jira/browse/PDFBOX-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated PDFBOX-3100:
--
Affects Version/s: 2.0.0
> Allow flexible calling of PageDra
[
https://issues.apache.org/jira/browse/PDFBOX-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated PDFBOX-3100:
--
Attachment: newpdfbox.patch
Patch im using
> Allow flexible calling of PageDra
simon steiner created PDFBOX-3100:
-
Summary: Allow flexible calling of PageDrawer
Key: PDFBOX-3100
URL: https://issues.apache.org/jira/browse/PDFBOX-3100
Project: PDFBox
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PDFBOX-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated PDFBOX-3100:
--
Component/s: Rendering
> Allow flexible calling of PageDra
rendering. You can
supply a custom PageDrawer but you can't create one which is independent of a
PDFRenderer. Note that PageDrawerParameters maintains a field which references
its parent PDFRenderer, so it's not possible to create one without the other.
You could subclass PDFRenderer and PageDrawer
[
https://issues.apache.org/jira/browse/PDFBOX-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson closed PDFBOX-3100.
---
Resolution: Won't Fix
> Allow flexible calling of PageDra
:
---
This is by design. PDFRenderer is the entry point for all rendering. You can
supply a custom PageDrawer but you can't create one which is independent of a
PDFRenderer. Note that PageDrawerParameters maintains a field which references
its parent PDFRenderer, so it's not possible to create one without
[
https://issues.apache.org/jira/browse/PDFBOX-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson resolved PDFBOX-2692.
-
Resolution: Fixed
Possibility to use our own and/or overwrite PageDrawer class
to use our own and/or overwrite PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue Type: Wish
Components
to use our own and/or overwrite PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue Type: Wish
Components
.
Possibility to use our own and/or overwrite PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue Type: Wish
Components
() belongs to the element that is
supposed to be green? As far as I understand the description from Daniel
Wilson, the application is not really change all red colors to green, but
change some of the elements on page to be green.
Possibility to use our own and/or overwrite PageDrawer class
the PageDrawer by myself, or? I
need all of its functionality, including transparency groups and all the other
logic it contains. I just need to intervene in showFontGlyph, or even
drawGlyph2D to tell to the target renderer draw a character instead of fill
path - if the renderer is capable
no knowledge of the structure of a PDF, nor should any subclass
thereof.
John, you are probably right that getStrokingPaint and getNonStrokingPaint
would need to be protected rather than private.
Possibility to use our own and/or overwrite PageDrawer class
elements - that's more complex than
what I'd first imagined. A Graphics2D isn't going to work for you in that case.
Possibility to use our own and/or overwrite PageDrawer class
Key: PDFBOX-2692
URL: https
to a device which implements Graphics2D
on top of PCL. I hadn't considered the case where your backend for a custom
PDFGraphicsStreamEngine would itself be a Graphics2D device. It's hard to argue
that subclassing PageDrawer wouldn't be a better option for you. I assume that
you're wanting to render
provided some further details on
their use cases which clearly show a need for subclassing PageDrawer. It's
apparent that there are benefits to this approach which outweigh my previous
concerns.
We need to keep the public API as small as possible, and not expose any of the
genuine (and unstable
PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue Type: Wish
Components: Rendering
Affects Versions: 2.0.0
provide PDFGraphicsStreamEngine which
provides easy, accurate and high-quality text and graphics stream processing
methods, which can be overridden. You will be able to rewrite your current 1.8
PageDrawer subclass in 2.0 as a PDFGraphicsStreamEngine subclass, with many
fewer lines of code
[
https://issues.apache.org/jira/browse/PDFBOX-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483530#comment-14483530
]
John Hewson commented on PDFBOX-2692:
-
-1 for making PageDrawer public. PageDrawer
instead?
Possibility to use our own and/or overwrite PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue Type: Wish
:
-
-1 for making PageDrawer public. PageDrawer is PDFBox's implementation of PDF
rendering to a Graphics2D surface, it is not a general-purpose graphics
extraction API - we already have one of those, it's PDFGraphicsStreamEngine
which was added specifically so that PageDrawer could be made private
:
--
That approach is obsolete in 2.0. We now provide PDFGraphicsStreamEngine which
provides easy, accurate and high-quality text and graphics stream processing
methods, which can be overridden. You will be able to rewrite your current 1.8
PageDrawer subclass in 2.0 as a PDFGraphicsStreamEngine
to override PageDrawer, I could intercept
showFontGlyph to tell the G2D implementation that the next fill() or draw() is
in fact drawing a letter in a given font.
Possibility to use our own and/or overwrite PageDrawer class
PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue Type: Wish
Components: Rendering
Affects Versions: 2.0.0
[
https://issues.apache.org/jira/browse/PDFBOX-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler updated PDFBOX-2692:
---
Fix Version/s: 2.0.0
Possibility to use our own and/or overwrite PageDrawer class
interfaces.
{quote}
Most of the API is already public as those methods are inherited from
PDFGraphicsStreamEngine and PDFStreamEngine. Even the order of calling those
methods is part of PDFStreamEngine and not of PageDrawer. There are 4 methods
which are public and would be exposed
functions that
eluded me.
Possibility to use our own and/or overwrite PageDrawer class
Key: PDFBOX-2692
URL: https://issues.apache.org/jira/browse/PDFBOX-2692
Project: PDFBox
Issue
of the API we're requesting seems quite
surgical.
If I manage to get the IKVM build going in Maven (as discussed in the mailing
list) will that assuage remaining objections?
Possibility to use our own and/or overwrite PageDrawer class
1 - 100 of 203 matches
Mail list logo
