I have purchased aspose.word product :
When we use “traditional Arabic” font and our document contains “Arabic diacritics (Tashkeel)” the generated pdf output became different than word (little space added between arabic letters ).
Please find the 2 attachments for screenshot of word and pdf:
DocumentBuilder.InsertWatermark Out.pdf (50.7 KB)
Word.png (202.7 KB)
[the generate word file](the word document url
this is the paragraph that has the issue :
أقْرَأُْ قِراءَةً صَحيحَةً مُحَرَّكَةً : لُبنَانُ وَطَنٌ حُرٌّ مُسْتَقِلٌّ ، نُرِيدُ أَنْ نَعيشَ شَعْباً سَيِّداً سَعِيداً ، في وَطَنٍ حُرٍّ مُسْتَقِلٍّ . كَتَبْتُ فَرْضاً نَظيفاً بِخَطٍّ جَميلٍ، وَدَرَسْتُ أُمْثُولَةً ، لَمْ تَكُنْ صَعْبَةً وَلَكِنَّها طَوِيلَةٌ . في يَوٍمِ عُطْلَةٍ قُمْنَا بِنُزْهَةٍ ، مَسَافَةٍ طَويلَةً مِنْ غَيْرِ تَعِبٍ ، وَقَدْ شَجَّعَنا على ذَلِك ، طَقٍسٌ جَميلٌ ، وَشَمْسٌ مُشْرِقَةٌ ، وَجَوٌّ مُعْتَدِلٌ
Thanks for your inquiry. Please note that Aspose.Words requires TrueType fonts when rendering document to fixed-page formats (JPEG, PNG, PDF or XPS). You need to install fonts that are used in your document on the machine where you’re converting documents to PDF. Please refer to the following article:
How Aspose.Words Uses True Type Fonts
If you still face problem, please ZIP and attach input Word document, fonts that are used in your document and code example that you are using to generate the PDF. We will investigate the issue on our side and provide you more information.
AsposeWord- issue project.zip (360.0 KB)
I used TrueType font called (“Traditional arabic” attached in the zip file).
the code is very simple and also attached.
Document doc = new Document( "test.docx"); // attached in the debug file
Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-16742. 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-16742) have been fixed in this Aspose.Words for .NET 22.5 update also available on NuGet.