Hello,
We are using aspose words to load documents from the database then print them. However Most of our documents contain custom Arabic Fonts which causes the aspose words to print mostly rubbish to the printer. We tried Setting the font source like this article, but with no luck.
Any help would be much appreciated.
Thank you,
Hi Abdulrahman,
Thanks for your inquiry. Please attach your input Word document and font files here for testing. We will investigate the issue on our end and provide you more information.
Best regards,
Hi,
I have attached a compressed file containing a test document and the custom fonts it uses.
this is in arabic, but im sure you will notice the differences between the actual document when you open/print it in word and the printed out version using aspose.
Thank you,
Hi Abdulrahman,
Thanks for your inquiry. Your Word document uses following fonts:
- Hacen Beirut Md
- Calibri
- Simplified Arabic
- Arial
On a Windows 7 machine, after an initial test with Aspose.Words 14.2.0, I was unable to reproduce this issue on my side. I used the following code for testing:
Document doc = new Document(MyDir + @"testFile.docx");
PrinterSettings ps = new PrinterSettings();
ps.PrinterName = "Microsoft XPS Document Writer";
ps.PrintToFile = true;
doc.Print(ps);
Could you please upgrade to the latest version of Aspose.Words and see how it goes on your end? I hope, this helps. Moreover, I have attached the printed XPS document here for your reference.
Best regards,
Hi,
No the document uses some of the fonts that i included in the zip file which are:
MCS Diwany2 S_I normal.
Simplified arabic.
I believe you generated the font names you mentioned using aspose library, please install the fonts on your test machine then use word to check the fonts used in the document.
Another thing, even in the XPS document you generated, the arabic font “simplified arabic” is not rendered right, i have attached an image to demonstrate that. I also attached two images comparing rendering of document using word and using aspose words, and I included a PDF generated from the same document using aspose.
Finally, we do have the latest version.
Thank you,
Hi Abdulrahman,
Thanks for the additional information. I have logged these problems in our issue tracking system as WORDSNET-9929 (PDF problem) and WORDSNET-9930 (XPS problem). We will further look into the details of these problems and keep you updated on the status of corrections. We apologize for your inconvenience.
Best regards,
Hi,
Any news about this issue??
Please note that this is an urgent matter.
Thank you.
Hi Abdulrahman,
Thanks for your inquiry. Unfortunately, your issues are not resolved yet. Please find below the progress of your issues:
WORDSNET-9929: Our development team is currently doing analysis of this issue.
WORDSNET-9930: This issue is pending for analysis and is in the queue.
We will inform you via this thread as soon as these issues are resolved. We apologize for your inconvenience.
Best regards,
Hi Abdulrahman,
Thanks for being patient. Regarding WORDSNET-9929, the provided fonts use some specific encoding for Arabic characters which is currently not supported by Aspose.Words. Unfortunately, we are not going to support this encoding in the nearest future because it seems to be obsolete. The implementation of the fix to this issue has been postponed till a later date. As a workaround please use Unicode fonts for Arabic characters. Moreover, we have logged WORDSNET-10205 and WORDSNET-10206 issues for the font fallback improvements. After fixing these two issues your document should be rendered better but the provided fonts still won’t be used. We apologize for your inconvenience.
Best regards,
So it took you 3 months to tell me there is no fix. This makes your product non-usable for me.
Hi Abdulrahman,
Thanks for your inquiry.
I am afraid, we had to postpone resolution of these issues because there are many other important issues we have to work on. These are complex issues and involve huge amount of work. However, the fixes to your issues may definitely come onto the product roadmap in the future. We will inform you via this thread as soon as these issues are resolved in future. We apologize for your inconvenience.
Moreover, WORDSNET-10205 has now been resolved and its fix will be included in next release of Aspose.Words 14.6.0. Your document should be rendered better.
Best regards,
The issues you have found earlier (filed as WORDSNET-10205) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
The issues you have found earlier (filed as WORDSNET-10206) have been fixed in this Aspose.Words for .NET 16.10.0 update and this Aspose.Words for Java 16.10.0 update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
@alkhouri,
Regarding WORDSNET-9929 and WORDSNET-9930, our product team has completed the work on your issues and has come to a conclusion that they won’t be able to implement the fixes to these issues because they are not going to implement support for an obsolete Font encoding. Your issues (WORDSNET-9929 and WORDSNET-9930) have now been closed with ‘Won’t Fix’ resolutions.