Hi,
Am 13.07.2010 14:08, schrieb Bruno Lowagie:
> This solves a problem caused by extra information that is added after
> the final "end" in the begin/end sequences in a ToUnicode stream?
> If so, then the patch is useful, I've added it to the SVN repository,
> and added an acknowledgment in the L
Andreas Ebbert-Karroum wrote:
> Good Morning,
>
> Am 12.07.2010 19:53, schrieb 1T3XT info:
>> Certainly! Thanks for the patch.
>> I'll try having a look at it tomorrow.
>>
>
> Ok, will you let me know, if you found it useful?
This solves a problem caused by extra information that is added af
Good Morning,
Am 12.07.2010 19:53, schrieb 1T3XT info:
> Certainly! Thanks for the patch.
> I'll try having a look at it tomorrow.
>
Ok, will you let me know, if you found it useful?
Thanks,
Andreas
--
This SF.net e
Andreas Ebbert-Karroum wrote:
> I've now patched the current trunk, it works for me with my limited
> understanding of PDF, etc. Maybe you want to consider it.
Certainly! Thanks for the patch.
I'll try having a look at it tomorrow.
--
This answer is provided by 1T3XT BVBA
http://www.1t3xt.com/ -
Hi,
Am 12.07.2010 14:00, schrieb 1T3XT info:
> Andreas Ebbert-Karroum wrote:
>
>> Not sure if this is still of interest to the others, who are subscribed
>> to the mailing list/group. I hope I don't annoy anybody. With the
>> knowledge, I could now probably fix that particular document, but
>>
Andreas Ebbert-Karroum wrote:
> Not sure if this is still of interest to the others, who are subscribed
> to the mailing list/group. I hope I don't annoy anybody. With the
> knowledge, I could now probably fix that particular document, but
> there's the risk, that the next document will show the
Am 12.07.2010 10:48, schrieb Andreas Ebbert-Karroum:
>
> >endbfchar
> endcmap CMapName currentdict /CMap defineresource pop end end
> D
> ><00p
>
> The byte array has a length of 561 and the error occurs after reading
> byte 558. When I look into the sources of PRTokeniser, this looks
> surprisin
Hi,
Am 12.07.2010 09:47, schrieb 1T3XT info:
>> I'm getting the error message as I posted in the stack trace. How
>> can I analyze from that, what particular part is causing that error?
>>
> > How can I tell?
>
> Look inside the PDF document.
>
Maybe this helps:
I've debugged into P
Hi,
Am 12.07.2010 09:47, schrieb 1T3XT info:
> Andreas Ebbert-Karroum wrote:
>
>> Maybe?
>>
> You'll have to check.
>
>
I'd love to :) I already installed a trial version of Adobe Acrobat Pro.
There's a content tool in Acrobat which allowed me to delete some parts
of the document,
Andreas Ebbert-Karroum wrote:
> Maybe?
You'll have to check.
> I'm getting the error message as I posted in the stack trace. How
> can I analyze from that, what particular part is causing that error?
> How can I tell?
Look inside the PDF document.
> Happy to try the snapshot. I'm currently ch
Hi,
Am 12.07.2010 09:16, schrieb 1T3XT info:
> Is this about inline images?
>
Maybe? I'm getting the error message as I posted in the stack trace. How
can I analyze from that, what particular part is causing that error?
> Is this about a font dictionary that can't be parsed?
>
How can I t
Andreas Ebbert-Karroum wrote:
> Hi,
>
> so far I have not received a reply to my question. If I can provide you
> with more detail or background, what do you still need to know? Or has
> the question already been answered somewhere? I'm also willing to patch
> iText myself, when I get a rough h
Hi,
so far I have not received a reply to my question. If I can provide you
with more detail or background, what do you still need to know? Or has
the question already been answered somewhere? I'm also willing to patch
iText myself, when I get a rough hint how and where.
We're currently blocke
Hi,
I'd like to discuss the problem again, that was mentioned in those posts
on the mailing list:
http://itext-general.2136553.n4.nabble.com/Inline-image-parsing-issue-td2260626.html
http://itext-general.2136553.n4.nabble.com/Re-not-expected-at-file-pointer-23512-td2172514.html
When I try to pa
14 matches
Mail list logo
