Hyperlinks breaking when saving as XPS

Hi,


I’m attempting to save a PDF file as an XPS, however if there is a hyperlink within the PDF file, the resulting XPS file looks like it has the hyperlink, but when it is clicked, nothing happens, it looks like the styling of the hyperlink is carried over, but not the actual functionality. I’m using the simple code snippet below as recommended in your documentation.

Document doc = new Document(pdf);
SaveOptions so = new XpsSaveOptions();
doc.Save(output, so);

Have you come across this issue before? Is there a fix for it?

Many thanks!

Hi Jak,


Thanks for contacting support.

Please share the resource PDF so that we can test the scenario in our environment. We are sorry for this inconvenience.

I’ve attached the 2 source files I am using, hopefully these will help

Hi Jak,

Thanks for sharing the resource files.

I have tested the scenario and I am able to notice the same problem: that the first hyperlink (local Child.pdf file) becomes corrupt. For the sake of correction, I have logged this problem as PDFNEWNET-38312 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. Please be patient and spare us a little time. We are sorry for this inconvenience.

Hi,


Is there any indication as to when we could potentially expect a fix for this issue, it’s starting to become a block in our development cycle.

If a fix isn’t possible, can one of your development team advise a work around on how we can still do the conversions while retaining the functionality of any links, be they web links or documents links.

Thanks for your help with this, much appreciated

Hi Jak,


Thanks for your patience.

As we recently have noticed the above stated issue, so its still pending for review and unless the team has investigated and figured out the reasons of this problem, we might not be able to share any possible timelines for its resolution. As soon as we have some definite news regarding its resolution, we will let you know.

Your patience and comprehension is greatly appreciated in this regard.

Hi Nayyer,


We’ve been in contact with Aspose in regards to purchasing priority support, obviously we are keen to get this issue resolved, as well as a few others we have outstanding with your .NET libraries as soon as possible.

The person we spoke to advised us to update this ticket since we are reluctant to purchase any additional support if it will not expedite this process, from our understanding, purchasing support would allow us to have a few issues flagged as a priority issue for resolution.

We were told that you should be able to provide some insight on whether or not the purchasing of support would help us get this issue resolved quicker?

Thanks again for the help in this issue.

Hi Jak,

Please note that as a normal rule of practice, issues are resolved on a first come and first serve basis; but the problems logged/reported under Enterprise or Priority support model, have high precedence in terms of resolution, as compared to issues under normal/free support model.

In case you need to have your issue prioritized, you may consider opting for Enterprise or Priority support options. Nonetheless, note that ES/PS support does not guarantee any immediate resolution of issues (because it might be dependent on other issues or features which need to be implemented) but under this model, the development team starts investigating the problem on high priority. For further details, please visit Support Options.

We are sorry for this delay and inconvenience.