We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Hyperlink encoding twise

Aspose.Words Product Family
#1
Hi Support Team,
I am using below code snippet to save the word document as pdf document.
Aspose.Words.Document doc = new Aspose.Words.Document(source);
doc.Save(destination, Aspose.Words.SaveFormat.Pdf);

In word document i am having hyper link url which is having space.So MS word is replacing space to %20 .
ex: www.google.com/North America changed as www.google.com/North%20America

And when i used above code snippet to convert the word document to pdf its again doing url encoding i guess.

After opening PDF i found url again changed as below

www.google.com/North%2520America

what would be the solution for this issue.
#2
Hi,

Thanks for your inquiry. After an initial test with Aspose.Words for .NET 17.1.0, we were unable to reproduce this issue on our end. We would suggest you please upgrade to the latest version of Aspose.Words. You can download it from the following link:
http://downloads.aspose.com/words/net

Please see output of following attachments is same:

msw-2016.pdf: This file was "Save As" by using MS Word 2016
17.1.0.pdf: This file was converted by using Aspose.Words for .NET 17.1.0.

Best regards,
#3

Hi Thanks for your reply.

How ever i tried with .NET 17.1.0 as you suggested .
But still issue i am facing.
See attached pictures and files which i tried with latest dll.

And also i found similar issue in the forum which is not yet resolved.

https://forum.aspose.com/t/22910&Subj=word-to-pdf-conversion-double-encodes-hyperlinks


http://mywebsite.com/sites/Shared%20Documents/myitems

When the document is converted to a PDF using Aspose.Words, the link is now:

http://mywebsite.com/sites/Shared%2520Documents/myitems

It appears that Aspose.Words is “re-encoding” the percent sign for the “%20” encoding, which means that this now becomes “%2520” (because “%25” is the percent encoding for the percent sign itself).

#4
Hi,

Thanks for your inquiry.

While using the latest version of Aspose.Words i.e. 17.1.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-14839. Your request has also been linked to the appropriate issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
#5

Hi Thanks for your response.

How soon we could expect the issue fix? Can you please let us know time frame?
#6

Hi,


Thanks for your inquiry. The fix of this issue will be included in Aspose.Words 17.3.0 release which will be published during the start of next month.

Best regards,
#7

The issues you have found earlier (filed as WORDSNET-14839) have been fixed in this Aspose.Words for .NET 17.3.0 update and this Aspose.Words for Java 17.3.0 update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.