have tested the scenario and I am able to reproduce the same problem. For the
sake of correction, I have logged it in our issue tracking system as PDFNEWNET-38886. We
will investigate this issue in details and will keep you updated on the status
of a correction. <o:p></o:p>
We apologize for your inconvenience.
Any update regarding this issue?
Unfortunately, there is no update on the linked ticket ID PDFNET-38886. It is on the high priority list under the free support model. We will let you know once it is fixed.
Our product team has plans to resolve and include this fix into the November, 2017 release (version 17.11). We will notify you once it is fixed.