[jira] [Commented] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[ https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120353#comment-17120353 ] Tilman Hausherr commented on PDFBOX-4853: - There is no "users-info" mailing list. No, 3.0 is not scheduled for release. You can use it, most is identical to 2.0, but the API can change. The best would be you take a snapshot, and have enough tests of your code (I suggest rendering comparison) to make sure all still works if you ever update to a new snapshot. > PDPageContentStream doesn't extend PDAbstractContentStream > -- > > Key: PDFBOX-4853 > URL: https://issues.apache.org/jira/browse/PDFBOX-4853 > Project: PDFBox > Issue Type: Improvement >Reporter: maltaisn >Priority: Minor > > Hi, > > I'm not sure if this is the right place to post this. I tried the FAQ mailing > list 2 weeks ago and didn't get any response so I'll try here. > > I'm creating a PDF with transparency groups so I need to use > PDFormContentStream, but also PDPageContentStream when not drawing to a > transparency group. Transparency groups can be arbitrarily nested so I keep a > stack of the current content stream to know which one to write to. > > However, what prevents me to keep the stack is that PDPageContentStream and > PDFormContentStream have no common interface despite sharing nearly all the > same methods. Is there any reason for this? I see there's already > PDAbstractContentStream that's being implemented by PDFormContentStream, > PDAppearanceContentStream PDPatternContentStream, but not by > PDPageContentStream... Why? > Currently this forces me to do [something like > that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an > interface for both. It's pretty ugly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Comment Edited] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[
https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120347#comment-17120347
]
maltaisn edited comment on PDFBOX-4853 at 5/30/20, 6:56 PM:
Thanks for the quick response.
{quote}
I don't see anything in the mailing list. What was the title?
{quote}
It was the users-info mailing list actually.
{quote}
What you are asking for is implemented in the trunk, but not in 2.0.*, probably
because it would break the API compatibility.
{quote}
I just checked it out and that's pretty much what I was asking for. Is this
scheduled for release soon? Or it'll have to wait until 3.0 because of the
breaking changes?
was (Author: maltaisn):
{quote}
I don't see anything in the mailing list. What was the title?
{quote}
It was the users-info mailing list actually.
{quote}
What you are asking for is implemented in the trunk, but not in 2.0.*, probably
because it would break the API compatibility.
{quote}
I just checked it out and that's pretty much what I was asking for. Is this
scheduled for release soon? Or it'll have to wait until 3.0 because of the
breaking changes? Thanks for the quick response.
> PDPageContentStream doesn't extend PDAbstractContentStream
> --
>
> Key: PDFBOX-4853
> URL: https://issues.apache.org/jira/browse/PDFBOX-4853
> Project: PDFBox
> Issue Type: Improvement
>Reporter: maltaisn
>Priority: Minor
>
> Hi,
>
> I'm not sure if this is the right place to post this. I tried the FAQ mailing
> list 2 weeks ago and didn't get any response so I'll try here.
>
> I'm creating a PDF with transparency groups so I need to use
> PDFormContentStream, but also PDPageContentStream when not drawing to a
> transparency group. Transparency groups can be arbitrarily nested so I keep a
> stack of the current content stream to know which one to write to.
>
> However, what prevents me to keep the stack is that PDPageContentStream and
> PDFormContentStream have no common interface despite sharing nearly all the
> same methods. Is there any reason for this? I see there's already
> PDAbstractContentStream that's being implemented by PDFormContentStream,
> PDAppearanceContentStream PDPatternContentStream, but not by
> PDPageContentStream... Why?
> Currently this forces me to do [something like
> that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an
> interface for both. It's pretty ugly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Comment Edited] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[
https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120347#comment-17120347
]
maltaisn edited comment on PDFBOX-4853 at 5/30/20, 6:55 PM:
{quote}
I don't see anything in the mailing list. What was the title?
{quote}
It was the users-info mailing list actually.
{quote}
What you are asking for is implemented in the trunk, but not in 2.0.*, probably
because it would break the API compatibility.
{quote}
I just checked it out and that's pretty much what I was asking for. Is this
scheduled for release soon? Or it'll have to wait until 3.0 because of the
breaking changes? Thanks for the quick response.
was (Author: maltaisn):
??I don't see anything in the mailing list. What was the title? ??
It was the users-info mailing list actually.
?? What you are asking for is implemented in the trunk, but not in 2.0.*,
probably because it would break the API compatibility. ??
I just checked it out and that's pretty much what I was asking for. Is this
scheduled for release soon? Or it'll have to wait until 3.0 because of the
breaking changes? Thanks for the quick response.
> PDPageContentStream doesn't extend PDAbstractContentStream
> --
>
> Key: PDFBOX-4853
> URL: https://issues.apache.org/jira/browse/PDFBOX-4853
> Project: PDFBox
> Issue Type: Improvement
>Reporter: maltaisn
>Priority: Minor
>
> Hi,
>
> I'm not sure if this is the right place to post this. I tried the FAQ mailing
> list 2 weeks ago and didn't get any response so I'll try here.
>
> I'm creating a PDF with transparency groups so I need to use
> PDFormContentStream, but also PDPageContentStream when not drawing to a
> transparency group. Transparency groups can be arbitrarily nested so I keep a
> stack of the current content stream to know which one to write to.
>
> However, what prevents me to keep the stack is that PDPageContentStream and
> PDFormContentStream have no common interface despite sharing nearly all the
> same methods. Is there any reason for this? I see there's already
> PDAbstractContentStream that's being implemented by PDFormContentStream,
> PDAppearanceContentStream PDPatternContentStream, but not by
> PDPageContentStream... Why?
> Currently this forces me to do [something like
> that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an
> interface for both. It's pretty ugly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[ https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120347#comment-17120347 ] maltaisn commented on PDFBOX-4853: -- ??I don't see anything in the mailing list. What was the title? ?? It was the users-info mailing list actually. ?? What you are asking for is implemented in the trunk, but not in 2.0.*, probably because it would break the API compatibility. ?? I just checked it out and that's pretty much what I was asking for. Is this scheduled for release soon? Or it'll have to wait until 3.0 because of the breaking changes? Thanks for the quick response. > PDPageContentStream doesn't extend PDAbstractContentStream > -- > > Key: PDFBOX-4853 > URL: https://issues.apache.org/jira/browse/PDFBOX-4853 > Project: PDFBox > Issue Type: Improvement >Reporter: maltaisn >Priority: Minor > > Hi, > > I'm not sure if this is the right place to post this. I tried the FAQ mailing > list 2 weeks ago and didn't get any response so I'll try here. > > I'm creating a PDF with transparency groups so I need to use > PDFormContentStream, but also PDPageContentStream when not drawing to a > transparency group. Transparency groups can be arbitrarily nested so I keep a > stack of the current content stream to know which one to write to. > > However, what prevents me to keep the stack is that PDPageContentStream and > PDFormContentStream have no common interface despite sharing nearly all the > same methods. Is there any reason for this? I see there's already > PDAbstractContentStream that's being implemented by PDFormContentStream, > PDAppearanceContentStream PDPatternContentStream, but not by > PDPageContentStream... Why? > Currently this forces me to do [something like > that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an > interface for both. It's pretty ugly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Comment Edited] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[ https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120331#comment-17120331 ] Tilman Hausherr edited comment on PDFBOX-4853 at 5/30/20, 6:08 PM: --- I don't see anything in the mailing list. What was the title? What you are asking for is implemented in the trunk, but not in 2.0.*, probably because it would break the API compatibility. was (Author: tilman): I don't see anything in the mailing list. What was the title? What you are asking for is implemented in the trunk, but not in 2.0.*, probably because it would break the API. > PDPageContentStream doesn't extend PDAbstractContentStream > -- > > Key: PDFBOX-4853 > URL: https://issues.apache.org/jira/browse/PDFBOX-4853 > Project: PDFBox > Issue Type: Improvement >Reporter: maltaisn >Priority: Minor > > Hi, > > I'm not sure if this is the right place to post this. I tried the FAQ mailing > list 2 weeks ago and didn't get any response so I'll try here. > > I'm creating a PDF with transparency groups so I need to use > PDFormContentStream, but also PDPageContentStream when not drawing to a > transparency group. Transparency groups can be arbitrarily nested so I keep a > stack of the current content stream to know which one to write to. > > However, what prevents me to keep the stack is that PDPageContentStream and > PDFormContentStream have no common interface despite sharing nearly all the > same methods. Is there any reason for this? I see there's already > PDAbstractContentStream that's being implemented by PDFormContentStream, > PDAppearanceContentStream PDPatternContentStream, but not by > PDPageContentStream... Why? > Currently this forces me to do [something like > that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an > interface for both. It's pretty ugly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[ https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120331#comment-17120331 ] Tilman Hausherr commented on PDFBOX-4853: - I don't see anything in the mailing list. What was the title? What you are asking for is implemented in the trunk, but not in 2.0.*, probably because it would break the API. > PDPageContentStream doesn't extend PDAbstractContentStream > -- > > Key: PDFBOX-4853 > URL: https://issues.apache.org/jira/browse/PDFBOX-4853 > Project: PDFBox > Issue Type: Improvement >Reporter: maltaisn >Priority: Minor > > Hi, > > I'm not sure if this is the right place to post this. I tried the FAQ mailing > list 2 weeks ago and didn't get any response so I'll try here. > > I'm creating a PDF with transparency groups so I need to use > PDFormContentStream, but also PDPageContentStream when not drawing to a > transparency group. Transparency groups can be arbitrarily nested so I keep a > stack of the current content stream to know which one to write to. > > However, what prevents me to keep the stack is that PDPageContentStream and > PDFormContentStream have no common interface despite sharing nearly all the > same methods. Is there any reason for this? I see there's already > PDAbstractContentStream that's being implemented by PDFormContentStream, > PDAppearanceContentStream PDPatternContentStream, but not by > PDPageContentStream... Why? > Currently this forces me to do [something like > that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an > interface for both. It's pretty ugly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Updated] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
[ https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] maltaisn updated PDFBOX-4853: - Description: Hi, I'm not sure if this is the right place to post this. I tried the FAQ mailing list 2 weeks ago and didn't get any response so I'll try here. I'm creating a PDF with transparency groups so I need to use PDFormContentStream, but also PDPageContentStream when not drawing to a transparency group. Transparency groups can be arbitrarily nested so I keep a stack of the current content stream to know which one to write to. However, what prevents me to keep the stack is that PDPageContentStream and PDFormContentStream have no common interface despite sharing nearly all the same methods. Is there any reason for this? I see there's already PDAbstractContentStream that's being implemented by PDFormContentStream, PDAppearanceContentStream PDPatternContentStream, but not by PDPageContentStream... Why? Currently this forces me to do [something like that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an interface for both. It's pretty ugly. was: Hi, I'm not sure if this is the right place to post this. I tried the FAQ mailing list 2 weeks ago and didn't get any response so I'll try here. I'm creating a PDF with transparency groups so I need to use PDFormContentStream, but also PDPageContentStream when not drawing to a transparency group. Transparency groups can be arbitrarily nested so I keep a stack of the current content stream to know which one to write to. However, what prevents me to keep the stack is that PDPageContentStream and PDFormContentStream have no common interface despite sharing nearly all the same methods. Is there any reason for this? I see there's already PDAbstractContentStream that's being implemented by PDFormContentStream, PDAppearanceContentStream PDPatternContentStream, but not by PDPageContentStream... Why? Currently this forces me to do [something like that](https://pastebin.com/p2FJw6GN) (Kotlin code) to artificially create an interface for both. It's pretty ugly. > PDPageContentStream doesn't extend PDAbstractContentStream > -- > > Key: PDFBOX-4853 > URL: https://issues.apache.org/jira/browse/PDFBOX-4853 > Project: PDFBox > Issue Type: Improvement >Reporter: maltaisn >Priority: Minor > > Hi, > > I'm not sure if this is the right place to post this. I tried the FAQ mailing > list 2 weeks ago and didn't get any response so I'll try here. > > I'm creating a PDF with transparency groups so I need to use > PDFormContentStream, but also PDPageContentStream when not drawing to a > transparency group. Transparency groups can be arbitrarily nested so I keep a > stack of the current content stream to know which one to write to. > > However, what prevents me to keep the stack is that PDPageContentStream and > PDFormContentStream have no common interface despite sharing nearly all the > same methods. Is there any reason for this? I see there's already > PDAbstractContentStream that's being implemented by PDFormContentStream, > PDAppearanceContentStream PDPatternContentStream, but not by > PDPageContentStream... Why? > Currently this forces me to do [something like > that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an > interface for both. It's pretty ugly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Created] (PDFBOX-4853) PDPageContentStream doesn't extend PDAbstractContentStream
maltaisn created PDFBOX-4853: Summary: PDPageContentStream doesn't extend PDAbstractContentStream Key: PDFBOX-4853 URL: https://issues.apache.org/jira/browse/PDFBOX-4853 Project: PDFBox Issue Type: Improvement Reporter: maltaisn Hi, I'm not sure if this is the right place to post this. I tried the FAQ mailing list 2 weeks ago and didn't get any response so I'll try here. I'm creating a PDF with transparency groups so I need to use PDFormContentStream, but also PDPageContentStream when not drawing to a transparency group. Transparency groups can be arbitrarily nested so I keep a stack of the current content stream to know which one to write to. However, what prevents me to keep the stack is that PDPageContentStream and PDFormContentStream have no common interface despite sharing nearly all the same methods. Is there any reason for this? I see there's already PDAbstractContentStream that's being implemented by PDFormContentStream, PDAppearanceContentStream PDPatternContentStream, but not by PDPageContentStream... Why? Currently this forces me to do [something like that](https://pastebin.com/p2FJw6GN) (Kotlin code) to artificially create an interface for both. It's pretty ugly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4848) Automate building website without local install
[ https://issues.apache.org/jira/browse/PDFBOX-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120224#comment-17120224 ] Andreas Lehmkühler commented on PDFBOX-4848: wrt to the configuration we could have a look at the Apache Camel build and ask on builds@ or infra@ if needed. [~msahyoun] lets start with moving from jekyll to maven as proposed. Maybe we should wait until 2.0.20 is released, just to ensure that we are able to update the download page of our website ;-) > Automate building website without local install > --- > > Key: PDFBOX-4848 > URL: https://issues.apache.org/jira/browse/PDFBOX-4848 > Project: PDFBox > Issue Type: Improvement > Components: Documentation >Reporter: Maruan Sahyoun >Assignee: Maruan Sahyoun >Priority: Minor > > As discussed on the dev mailing list we are looking to utilize the [git - > .asf.yaml > features|https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features] > and/or other capabilities to simplify building the website without the need > to install the site generation locally. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
Re: Release 2.0.20 ?
@Tim Cool, yes, please! I'm going to postpone the release for a couple of days depending on the results. Thanks in advance! Andreas Am 30.05.20 um 12:59 schrieb Tim Allison: I can run the tests on Monday w results by the end of the day EDT if desired. On Sat, May 30, 2020 at 5:53 AM Andreas Lehmkuehler wrote: Hi, I just realized that we didn't run Tims tests yet. I've had a look at the tickets and most of them are not related to text extraction. The remaining are mostly dealing with corner cases so that we should be save. WDYT, are we save enough or do we need to run the tests before cutting the release? Andreas Am 26.05.20 um 08:02 schrieb Andreas Lehmkuehler: I'm planning to cut the release on next Monday 1st of June. Andreas Am 20.05.20 um 08:15 schrieb Andreas Lehmkuehler: Hi, how about cutting a 2.0.20 release in 2 or 3 weeks from now? Andreas - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
Re: Release 2.0.20 ?
I can run the tests on Monday w results by the end of the day EDT if desired. On Sat, May 30, 2020 at 5:53 AM Andreas Lehmkuehler wrote: > Hi, > > I just realized that we didn't run Tims tests yet. I've had a look at the > tickets and most of them are not related to text extraction. The remaining > are > mostly dealing with corner cases so that we should be save. > > WDYT, are we save enough or do we need to run the tests before cutting the > release? > > Andreas > > Am 26.05.20 um 08:02 schrieb Andreas Lehmkuehler: > > I'm planning to cut the release on next Monday 1st of June. > > > > Andreas > > > > Am 20.05.20 um 08:15 schrieb Andreas Lehmkuehler: > >> Hi, > >> > >> how about cutting a 2.0.20 release in 2 or 3 weeks from now? > >> > >> Andreas > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org > >> For additional commands, e-mail: dev-h...@pdfbox.apache.org > >> > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org > > For additional commands, e-mail: dev-h...@pdfbox.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org > For additional commands, e-mail: dev-h...@pdfbox.apache.org > >
[jira] [Resolved] (PDFBOX-4851) Image rendering issue 2
[ https://issues.apache.org/jira/browse/PDFBOX-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr resolved PDFBOX-4851. - Fix Version/s: 3.0.0 PDFBox 2.0.20 Assignee: Tilman Hausherr Resolution: Fixed Should work now. Thanks for the report! > Image rendering issue 2 > --- > > Key: PDFBOX-4851 > URL: https://issues.apache.org/jira/browse/PDFBOX-4851 > Project: PDFBox > Issue Type: Bug > Components: FontBox, Rendering >Affects Versions: 2.0.19 >Reporter: Daniel Persson >Assignee: Tilman Hausherr >Priority: Minor > Fix For: 2.0.20, 3.0.0 PDFBox > > Attachments: PDFBOX-4851-reduced3.pdf, issue2-pdfbox.jpg, > issue2-poppler.jpg, issue2.pdf, mercury.ttf > > > Text is missing in image rendered using PDFToImage. > > Text is present if you render with Poppler instead. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Updated] (PDFBOX-4851) Image rendering issue 2
[ https://issues.apache.org/jira/browse/PDFBOX-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr updated PDFBOX-4851: Component/s: FontBox > Image rendering issue 2 > --- > > Key: PDFBOX-4851 > URL: https://issues.apache.org/jira/browse/PDFBOX-4851 > Project: PDFBox > Issue Type: Bug > Components: FontBox, Rendering >Affects Versions: 2.0.19 >Reporter: Daniel Persson >Priority: Minor > Attachments: PDFBOX-4851-reduced3.pdf, issue2-pdfbox.jpg, > issue2-poppler.jpg, issue2.pdf, mercury.ttf > > > Text is missing in image rendered using PDFToImage. > > Text is present if you render with Poppler instead. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4851) Image rendering issue 2
[ https://issues.apache.org/jira/browse/PDFBOX-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120180#comment-17120180 ] ASF subversion and git services commented on PDFBOX-4851: - Commit 1878311 from Tilman Hausherr in branch 'pdfbox/branches/2.0' [ https://svn.apache.org/r1878311 ] PDFBOX-4851: swallow exception when reading PostScript table and set default values > Image rendering issue 2 > --- > > Key: PDFBOX-4851 > URL: https://issues.apache.org/jira/browse/PDFBOX-4851 > Project: PDFBox > Issue Type: Bug > Components: Rendering >Affects Versions: 2.0.19 >Reporter: Daniel Persson >Priority: Minor > Attachments: PDFBOX-4851-reduced3.pdf, issue2-pdfbox.jpg, > issue2-poppler.jpg, issue2.pdf, mercury.ttf > > > Text is missing in image rendered using PDFToImage. > > Text is present if you render with Poppler instead. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4851) Image rendering issue 2
[ https://issues.apache.org/jira/browse/PDFBOX-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120179#comment-17120179 ] ASF subversion and git services commented on PDFBOX-4851: - Commit 1878310 from Tilman Hausherr in branch 'pdfbox/trunk' [ https://svn.apache.org/r1878310 ] PDFBOX-4851: swallow exception when reading PostScript table and set default values > Image rendering issue 2 > --- > > Key: PDFBOX-4851 > URL: https://issues.apache.org/jira/browse/PDFBOX-4851 > Project: PDFBox > Issue Type: Bug > Components: Rendering >Affects Versions: 2.0.19 >Reporter: Daniel Persson >Priority: Minor > Attachments: PDFBOX-4851-reduced3.pdf, issue2-pdfbox.jpg, > issue2-poppler.jpg, issue2.pdf, mercury.ttf > > > Text is missing in image rendered using PDFToImage. > > Text is present if you render with Poppler instead. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4851) Image rendering issue 2
[ https://issues.apache.org/jira/browse/PDFBOX-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120181#comment-17120181 ] ASF subversion and git services commented on PDFBOX-4851: - Commit 1878312 from Tilman Hausherr in branch 'pdfbox/branches/issue45' [ https://svn.apache.org/r1878312 ] PDFBOX-4851: swallow exception when reading PostScript table and set default values > Image rendering issue 2 > --- > > Key: PDFBOX-4851 > URL: https://issues.apache.org/jira/browse/PDFBOX-4851 > Project: PDFBox > Issue Type: Bug > Components: Rendering >Affects Versions: 2.0.19 >Reporter: Daniel Persson >Priority: Minor > Attachments: PDFBOX-4851-reduced3.pdf, issue2-pdfbox.jpg, > issue2-poppler.jpg, issue2.pdf, mercury.ttf > > > Text is missing in image rendered using PDFToImage. > > Text is present if you render with Poppler instead. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
Re: Release 2.0.20 ?
Hi, I just realized that we didn't run Tims tests yet. I've had a look at the tickets and most of them are not related to text extraction. The remaining are mostly dealing with corner cases so that we should be save. WDYT, are we save enough or do we need to run the tests before cutting the release? Andreas Am 26.05.20 um 08:02 schrieb Andreas Lehmkuehler: I'm planning to cut the release on next Monday 1st of June. Andreas Am 20.05.20 um 08:15 schrieb Andreas Lehmkuehler: Hi, how about cutting a 2.0.20 release in 2 or 3 weeks from now? Andreas - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
