Mailing-List: contact users-help@pdfbox.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@pdfbox.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Problem reading PDF with Type1 font
From: John Hewson <john@jahewson.com>
In-Reply-To: <5784FDF6.3020300@thomas-letsch.de>
Date: Tue, 12 Jul 2016 19:44:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <181A6240-572B-4C4B-B7BB-DAB8FDDF9669@jahewson.com>
References: <5784DFFA.5050206@thomas-letsch.de> <3a071e07-6cdc-5d2a-12b5-e58aec2dfa62@lehmi.de> <5784EE3C.6000709@thomas-letsch.de> <3f83fa6d-2418-e4ea-baba-771fe0496eb1@lehmi.de> <5784FDF6.3020300@thomas-letsch.de>
To: users@pdfbox.apache.org
archived-at: Wed, 13 Jul 2016 02:44:41 -0000


> On 12 Jul 2016, at 07:25, Thomas Letsch <contact@thomas-letsch.de> =
wrote:
>=20
> Am 12.07.2016 um 16:15 schrieb Andreas Lehmkuehler:
>> Am 12.07.2016 um 15:18 schrieb Thomas Letsch:
>>> Hi Andreas,
>>>=20
>>> thanks for your answer.
>>>=20
>>> Am 12.07.2016 um 15:01 schrieb Andreas Lehmkuehler:
>>>> Hi,
>>>>=20
>>>> Am 12.07.2016 um 14:18 schrieb Thomas Letsch:
>>>>> Hi,
>>>>>=20
>>>>> I am reading a PDF file with an embedded type1 font. I am getting =
an
>>>>> IOException during parsing of the PDF (I removed the name of the =
font
>>>>> for legal reasons):
>>>> Why not, is it a secret font?
>>> Actually I don't know. The whole PDF is confidential, so any part of =
it
>>> is probably, too. And its not a common font you find on the web.
>> But maybe some of the devs have access to that font. Saying that, =
what
>> is the name of that specific font?
> You are right, probably me being too strict. Its called =
ARTWAB+Helvetica.

That=E2=80=99s a subset. So we=E2=80=99re going to need that actual font =
file. You can extract it from the PDF
using our GUI-baed PDFDebugger . Navigate to the page in question, and =
find the Font=20
resource with that name. Right-click on the FontFile resource in the =
tree and save the
stream to a .pfb file. Then send us that file.

=E2=80=94 John

>>=20
>>>>=20
>>>>> PDType1Font [ERROR] Can't read the embedded Type1 font <name =
removed>
>>>>> java.io.IOException: Found Token[kind=3DSTART_ARRAY, text=3D[] but
>>>>> expected
>>>>> INTEGER
>>>>>=20
>>>>> Unfortunately I cannot send you the PDF, but I can send you an =
extract
>>>>> with the (hopefully) interesting parts.
>>>> I doesn't help. We need the font itself as the parser throws the
>>>> exception when reading the font.
>>> This is my fault, I didn't include the whole stack trace. Sorry, =
here
>>> it is:
>>> java.io.IOException: Found Token[kind=3DSTART_ARRAY, text=3D[] but =
expected
>>> INTEGER
>>>    at =
org.apache.fontbox.type1.Type1Parser.read(Type1Parser.java:754)
>>>    at
>>> =
org.apache.fontbox.type1.Type1Parser.readEncoding(Type1Parser.java:200)
>>>    at
>>> =
org.apache.fontbox.type1.Type1Parser.parseASCII(Type1Parser.java:128)
>>>    at =
org.apache.fontbox.type1.Type1Parser.parse(Type1Parser.java:61)
>>>    at
>>> =
org.apache.fontbox.type1.Type1Font.createWithSegments(Type1Font.java:85)
>>>    at
>>> =
org.apache.pdfbox.pdmodel.font.PDType1Font.<init>(PDType1Font.java:228)
>>>    at
>>> =
org.apache.pdfbox.pdmodel.font.PDFontFactory.createFont(PDFontFactory.java=
:62)
>>>=20
>>>    at
>>> org.apache.pdfbox.pdmodel.PDResources.getFont(PDResources.java:123)
>>>    at
>>> =
org.apache.pdfbox.contentstream.operator.text.SetFontAndSize.process(SetFo=
ntAndSize.java:60)
>>>=20
>>>    at
>>> =
org.apache.pdfbox.contentstream.PDFStreamEngine.processOperator(PDFStreamE=
ngine.java:815)
>>>=20
>>>    at
>>> =
org.apache.pdfbox.contentstream.PDFStreamEngine.processStreamOperators(PDF=
StreamEngine.java:472)
>>>=20
>>>    at
>>> =
org.apache.pdfbox.contentstream.PDFStreamEngine.processStream(PDFStreamEng=
ine.java:446)
>>>=20
>>>    at
>>> =
org.apache.pdfbox.contentstream.PDFStreamEngine.processPage(PDFStreamEngin=
e.java:149)
>>>=20
>>>=20
>>> This looks for my non-expert eyes like a problem in reading the
>>> encoding. At least this is my hope, because then we perhaps can get
>>> along without the font file.
>> The parser has a problem with reading the _internal_ encoding of the
>> font, which has nothing to do with the encoding within the pdf =
itself.
>> There are 2 possible issues, either the font is malformed or our
>> parser has a bug and unfortunately we need the font itself to find =
out.
> Ok, I understand.
>=20
> Best Regards,
> Thomas
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org