<HTML xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<HEAD><!-- Template generated by Exclaimer Mail Disclaimers on 03:04:56 Tuesday, 10 October 2017 -->
<STYLE type=text/css>P.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
LI.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
DIV.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
TABLE.ImprintUniqueIDTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!-- Template generated by Exclaimer Mail Disclaimers on 03:04:56 Tuesday, 10 October 2017 -->
<STYLE type=text/css>P.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
LI.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
DIV.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
TABLE.ImprintUniqueIDTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</STYLE>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="Generator" content="Microsoft Word 15 (filtered medium)" />
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.imprintuniqueid, li.imprintuniqueid, div.imprintuniqueid
{mso-style-name:imprintuniqueid;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.E-MailFormatvorlage18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.E-MailFormatvorlage20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</HEAD>
<BODY bgcolor="white" lang="DE" link="#0563C1" vlink="#954F72">
<P class=ImprintUniqueID>
<P class=ImprintUniqueID>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D>Hi Alexey,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D>We are tried to fix this issue within iText but until now without success.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D>It seems that viewing the Adobe Acrobat PDF viewer displays the PDF file “a1_attachment-1-page-3.pdf” without an error. I think that in such a case, it would be better if XEP would create a PDF image
rather than not create a PDF image. Do you think you can do this in XEP? That would help us a lot. Thank you very much in advance for your support!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D>Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D>Uwe Goersch<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style=color:#1F497D><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style=color:windowtext;mso-fareast-language:DE>Von:</span></b><span lang="EN-US" style=color:windowtext;mso-fareast-language:DE> Xep-support [mailto:xep-support-bounces@renderx.com]
<b>Im Auftrag von </b>Alexey Gagarinov<br/>
<b>Gesendet:</b> Samstag, 2. September 2017 02:50<br/>
<b>An:</b> STRECKWALDT, TILL <till.streckwaldt@lhind.dlh.de><br/>
<b>Cc:</b> RenderX Community Support List <xep-support@renderx.com><br/>
<b>Betreff:</b> [xep-support] Re: XEP 4.23 NullPointerException<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style=margin-bottom:12.0pt><span lang="EN-US">Hi Till,</span><span lang="EN-US" style=font-size:12.0pt;mso-fareast-language:DE><o:p></o:p></span></p>
</div>
<blockquote style=margin-top:5.0pt;margin-bottom:5.0pt>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:DE">when using XEP 4.23 to create a PDF file with an additional PDF attachment, there is a NullPointerException and the resulting PDF cannot
be read. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style=margin-bottom:12.0pt><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:DE"><br/>
It's a 'a1_attachment-1-page-3.pdf' that cause the NPE.<br/>
<br/>
This PDF file is a TOC and contains links.<br/>
Each link itself is an annotations with a GoTo action (in terms of PDF Specification).<br/>
In more simple words: you click on the link and will be forwarded to some place on other page.<br/>
<br/>
A PDF splitting software (iText in your case) correctly removes all objects from other pages, but keeps the "hanging" links.<br/>
By "hanging" I mean an indirect PDF object reference without the PDF object itself.<br/>
For example,<br/>
<br/>
<</D[20 0 R/XYZ 52 715 0.0]/S/GoTo>><br/>
<br/>
where 20 0 R is the indirect reference to another page, but the obj #20 (20 0 R) itself is absent in the PDF file.<br/>
<br/>
In such a case XEP fails to create a PDF image.<br/>
And, in my opinion, it's the most reasonable behavior -- no PDF image when parsing of the PDF is failed.<br/>
Not with NPE, of course :) -- it's our fault, I will fix.<br/>
<br/>
I believe it's worth to ping iText about removing "hanging" indirect objects for links (PDF Annots) during splitting a PDF file.<br/>
<br/>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:DE">---<br/>
With best regards,<br/>
Alexey Gagarinov<br/>
RenderX<o:p></o:p></span></p>
</div>
</P>
<P class=ImprintUniqueID></P></P>
<P class=ImprintUniqueID> </P>
<P class=ImprintUniqueID><FONT size=1 face=Arial><FONT color=#7d7d7d>Sitz der
Gesellschaft / Corporate Headquarters: Lufthansa Industry Solutions BS GmbH,
Raunheim, Registereintragung / Registration: Amtsgericht Darmstadt HRB
83850<BR/>Geschaeftsfuehrung / Management Board: Bernd
Appel<BR/><BR/></FONT><BR/><BR/></FONT></P></BODY>
</HTML>