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

Free Support Forum - aspose.com

Unexpected bolded charcters after converting .doc to pdf

Dear support team,
we are using Aspose.Words within one of our .NET application. Generally speaking our application enables the user to create specific documents in word format (.doc) . Further it provides the option to convert these documents to pdf, using Aspose.
Unfortunately we discovered a problem recently related to this pdf conversion:
When converting a generated .doc file to pdf with Aspose.Pdf, all non-bolded characters within the documents become bold and vice versa.
Please find an example attached.
The .doc file within the attachment was converted to pdf, resulting in the pdf file that contains the unexpected bolded characters.
Could you please help us to solve this problem?
Thanks & best regards,
Robin

Hi Robin,

Thanks for your inquiry. After an initial test with Aspose.Words for .NET 14.3.0, I was unable to reproduce this issue on my side (please see attached out.pdf). I would suggest you please upgrade to the latest version of Aspose.Words. You can download it from the following link. I hope, this helps.
https://releases.aspose.com/words/net

Best regards,

Hi Awais,
thanks, we’ll try again with the latest version than.
Best,
Robin

Hi again,
using the latest version seems to bring the expected result, so thanks again for the hint!
However after converting to PDF there is a large space after the first red line on page 1, right after the blue text. This white space is not present in the initial document.
Please compare the initial word document from our first post and the PDF that resulted from converting via Aspose. (issue occures in our and in your PDF output )
Any idea where this large white space might be coming from?
Thanks in advance and best regards,
Robin

Hi Robin,

Thanks for reporting this problem to us. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-10045. Your thread has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,

Hi,
do you have any news for use regarding this issue?
We are planning to extend our company licence, however before doing so we need to be sure that this issue has been fixed in the latest version.
Many thanks in advance and best regards,
Robin

Hi Robin,

Thanks for your inquiry.

Regarding WORDSNET-10045, unfortunately at the moment we cannot provide you any reliable estimate. Our development team has completed the analysis of this issue and the root cause has been identified. However, the implementation of the fix of this issue has been postponed till a later date. We will inform you as soon as this issue is resolved. We apologize for your inconvenience.

We understand that this issue is important to you; normally when an issue is reported by a customer via Aspose.Words forum, it is added to the pool of current issues being worked on by our developers. Our developers work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers. However, due to the nature of some bugs and the number of features we are working on, this doesn’t always mean we can fix every bug within a short time after it’s reported.

That being said, we fully understand that you are keen to get a fix to your particular issue, please have a look at enhanced support options - e.g. purchasing Priority Support will allow you to post your issues in our Priority Support forum and raise the priority of these issues directly with our development teams, if possible, we will then aim to get a resolution to your issue as soon as we can. Many Priority Support customers find that this leads to their issue being fixed in the next release of the software.

If you would like to take advantage of Enhanced Support then please request a quote in our purchase forum -https://forum.aspose.com/c/purchase/6

Best regards,

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


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