Hi,
An exception occurs when converting RTF files with bullets and active hyphenation.
As an example, I attached a file. If the hyphenation is off or no line is longer than the page width, there is no error. The error only occurs with RTF files.
Version Aspose.Word für .NET = 20.2.0.0
WIN 10
t4.zip (11.1 KB)
Thank you for your help.
Steffen Rassek
@rassekst
To ensure a timely and accurate response, please attach the following resources here for testing:
- Please attach the output file that shows the undesired behavior.
- Please attach the expected output file that shows the desired behavior.
- Please create a standalone console application ( source code without compilation errors ) that helps us to reproduce your problem on our end and attach it here for testing.
As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.
PS: To attach these resources, please zip and upload them.
Hi,
Is there already a solution to the problem?
Best regards,
Steffen
@rassekst
We need code example that you are using to reproduce this issue at our end. Please share sample code example for testing. Thanks for your cooperation.
Here is the test code.
SteffenTest4.zip (5.4 MB)
@rassekst
We have used your code to test this case and managed to reproduce the same issue at our side. This issue has been logged as WORDSNET-20926 . You will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSNET-20926) have been fixed in this Aspose.Words for .NET 20.9 update and this Aspose.Words for Java 20.9 update.
Hi,
Unfortunately there are still problems with converting Word documents to PDF. I am currently using version 20.10.0 and it crashes when the hyphenation is switched on.
Can you look at that again, please?
thank you for your help
Steffenerror.zip (82.0 KB)
@rassekst
We have logged this problem in our issue tracking system as WORDSNET-21378. You will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.