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

Free Support Forum - aspose.com

Error converting RTF (comprising both english and arabic text) to PDF

I am trying to evaluate Aspose.Words for .NET.
I want to convert RTF documents (created using DevExpress’ XtraReports for .NET component) to PDF, but the order of arabic words is reversed by the conversion.
I have attached example files where you can see the problem.
Is there a solution for this ?

Please advise



Hi John,

Thanks for your inquiry. I have tested the scenario by using latest version of Aspose.Words and have not found any issue with output Pdf/Xps. I suggest you please upgrade to latest version of Aspose.Words for .NET 13.6.0 from here:

I have attached the output Pdf/Xps with this post for your kind reference. Please let us know if you have any more queries.

Hi Tahir,

Thanks for your reply.
I had used the latest (trial) version 13.6.0 of Aspose.Words to do the conversion.
I don’t know if there is something wrong in the contents of the RTF file but what is actually happening is this :
If you open the RTF file with MS Word you see, for example, the text “Client Name / العميل اسم” (which is not correct).
But, if you add an Arabic language in your Keyboard (Region And Language > Keyboards and Languages) then you will see the text “Client
Name / اسم العميل
” (the order of the 2 arabic words is reversed), which is the correct form of the arabic text.
You can see the same image in the attached XPS file of my first message (which is also created by DevExpress’ XtraReports).
Now, the resulting PDF file converted from RTF by Aspose.Words is always in the wrong form (whether arabic language was added in Keyboard or not).

Thanks again


Hi John,

Thanks for sharing the detail. I have managed to reproduce the same issue at my side. I have logged this issue as WORDSNET-8681 in our issue tracking system. I have linked this forum thread to the same issue and 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-8681) have been fixed in this Aspose.Words for .NET 18.11 update and this Aspose.Words for Java 18.11 update.