Hi,
I came accross this article
https://www.pdfa.org/safedocs-unearths-pdf-inline-image-issue/ at the PDF
Association web. It describes what should happen if an inline image contains
both an abbreviated and a full key for the same thing, but each having a
different value. I have checked the exa
t you
expected.
https://issues.apache.org/jira/browse/PDFBOX-4135
Tilman
Am 26.02.2018 um 21:43 schrieb Petr Slabý:
Thanks for the great news and great work. I have added it to my
dependencies and it downloaded fine from the apache maven repository.
I have noticed, that the poms in the P
Thanks for the great news and great work. I have added it to my dependencies
and it downloaded fine from the apache maven repository.
I have noticed, that the poms in the PDFBox projects still reference the
original levigo library. I guess that is the next step?
Best regards,
Petr.
-Půvo
Hi,
are there any plans to release the JBIG2 ImageIO Plugin (PDFBOX-3906) ?
Personally, I would like to see that happen as soon as possible. We are not
able to distribute the original Levigo library because of its licence, so I am
looking forward to distribute the PDFBox JBIG2 plugin alongside w
Hi,
I have a PDF which cannot be read by PDFBox 1.8.x, but works fine in PDFBox
2.x. Before I create an issue I need to internally clarify whether I can share
the PDF. And I would like to clarify with you whether it makes sense to create
an issue at all.
The problem in the PDF is the following.
Hi,
your message caught my attention, so I could not resist to try and
investigate it a little. I did not get too far and do not have the time to
do any tests, but maybe at least a small hint. To at least have a chance
that the sun java2d machinery draws the image without converting it first,
Hi,
does that mean that you are free of bug reports from now on? That is a great
invention, we should make the same in our company internal JIRA, that would
save a lot of work to me :-)
Can you please add me to a group which is allowed to post issues, too?
Best regards,
Petr.
-Původní zp
Hi,
Sorry, please can you answer all of the questions in my previous mail or I
can’t help you.
Not sure whether I need any help right now. All I wanted to do is to vote
for the "per-document FontMapper or FontProvider" solution and explain some
reasons for that.
Now searching for question
nd postpone the 2.0 release
by yet another year, I will rather live with what we have now.
Best regards,
Petr.
-Původní zpráva-
From: John Hewson
Sent: Wednesday, September 02, 2015 4:43 AM
To: dev@pdfbox.apache.org
Subject: Re: Font provider since PDFBOX-2842
On 1 Sep 2015, at 06
John,
I am facing basically the same issues as Cornelis.
Our application is running in a J2EE application server, so installing
anything into the operation system is usually not an option. It is already
difficult in a cluster environment managed by the customer, but becomes
virtually impossib
Hi,
as so many other users, I would appreciate a pdfbox version 2.0 release as
soon as possible. Or at least a plan for it.
In our project, we suffer from the same problems as described by Simon. In
our release plan, we had the move to pdfbox 2.0 planned for this year. But
the APIs are chang
Hi,
following is a description of what we are doing in our company.
With our software, we run regression tests after each nightly build and
sometimes it is a tough fight. If there is a regression, it is not so easy
to find which commit caused it, because there are potentially many between
the
Hi,
do you know whether Oracle has an issue for that and/or whether they plan to
fix it? The same problem happens with the last java 1.6 update as well
(1.6_u43). Or at least I assume that this issue is about the problem caused
by java.awt.Font not being able to read Type1 fonts embedded in PDF
patch against PDFBOX trunk.
Thanks,
Timo
Am 30.01.2014 11:34, schrieb Petr Slabý:
Hi,
according to
https://developer.apple.com/fonts/TTRefMan/RM06/Chap6loca.html, the “loca”
table is supposed to contain glyphcount+1 offset. If an index of a glyph
is the same as the offset of the previous one
Hi,
according to https://developer.apple.com/fonts/TTRefMan/RM06/Chap6loca.html,
the “loca” table is supposed to contain glyphcount+1 offset. If an index of a
glyph is the same as the offset of the previous one, the glyph has no data
(does not exist in the font). The code of initData() in GlyphT
15 matches
Mail list logo