> On 13 Jul 2016, at 02:16, Thomas Letsch <[email protected]> wrote:
> 
> Hi John,
> 
> I am really sorry, but I spoke with my colleges and we may not give out
> even the fonts.
> 
> I could try and debug it on my machine if there are some hints about
> what to check.

Launch with a debugger attached and when the exception is thrown, find
the ”parseASCII" method in the call stack and save the "bytes” array to a .txt
file. This contains only the ASCII portion of the font, which you can easily 
read
by eye and see that it contains no sensitive information. Once you’ve confirmed
that, send us the .txt file.

— John

> Thanks for your help,
> Thomas
> 
> Am 13.07.2016 um 04:44 schrieb John Hewson:
>> You are right, probably me being too strict. Its called ARTWAB+Helvetica.
>> That’s a subset. So we’re 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 
>> 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.
>> 
>> — John
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to