Hello
Our company purchased Aspose.Words for Java API version 16.4.0 (aspose-words-16.4.0-jdk16) about three month ago and we faced to an error in conversion of Microsoft word files to PDF when it contains IranNastaliq font. Although according to issue id “WORDSNET-13025” that says it would have been solved in version of 15.12.0, but it had not been solved yet. It’s vital for our that it will be solved asap.
Sincerely
Link:
Save Persian Text Formatted with IranNastaliq Font in DOC DOCX to PDF File using Java API
Hi Ali,
Thanks for your inquiry. The issue (WORDSNET-13025) has been postponed because it requires advanced typography feature which is not supported by Aspose.Words. We have already logged this feature request as WORDSNET-6633 in our issue tracking system. We will inform you via this forum thread once there are any further developments.
We apologize for your inconvenience.
Dear tahir,
Your response to Issue numbers WORDSNET-6633 and WORDSNET-13025 is now very critical to our software. I’d be grateful if you could let us know your plans about solving the above issues ASAP.
Thanks for your inquiry. We regret to share with you that this feature is still postponed. I am afraid, there is no estimate available at the moment. However, we have asked for the ETA of this feature from our product team. As soon as any information is shared by them, we will be more than happy to share that with you.
We apologize for your inconvenience.
Dear tahir,
Thank you for your reply. Would our readiness for financial sponsorship effect your company’s decision on working to solve this issue? In that case how much would be the cost of this sponsorship and how long will it take to solve the problem? Do you need our technical staff’s help on details of Nastaliq font?
Regards
Please accept my apologies for your inconvenience.
Normally when an issue is reported by a customer it is added to the pool of current issues being worked on by our developers and is analysed in a timely manner. 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.
This is a big feature and we will check possible ways to implement it. Hopefully, this feature will be available in the second quarter of 2018. Please note that this estimate is not final at the moment; we will be sure to inform you via this forum thread as soon as this feature is available.
Thank you for your patience and understanding.
Hi,
Do you support Opentype fonts? If not do you have a plan to do so in near future?
regards,
Abbas Dehghani
Thanks for your inquiry. Aspose.Words supports both True Type and Open Type fonts during rendering Word documents to fixed page format e.g. PDF, XPS.
In “Traditional Arabic” font( which is standard default font of windows for Arabic and Farsi language) the two characters 062D and 0644 should be presented by one single code FC40 لح Glyph (according to OpenType Table inside TTF font file), but this table is ignored by Aspose and it is wrongly presented by two consecutive glyphs of FEA2 and FEDE ( لح ). Is there any means in Aspose to show this glyph as its original one code shape which is in Word Document?
Thanks for your inquiry. Please ZIP and attach your input Word document and fonts here for testing. We will investigate the issue on our side and provide you more information.
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-15858. You will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
Hi,
Is there any progress on our case no. 15858?
Thanks for your inquiry. You issue is related to advanced typography feature (WORDSNET-6633) which is not supported by Aspose.Words. We regret to share with you that this feature has been postponed. We will inform you via this forum thread once there are any further developments.
We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSNET-15858) have been fixed in this Aspose.Words for .NET 20.5 update and this Aspose.Words for Java 20.5 update.
The issues you have found earlier (filed as WORDSNET-13025) have been fixed in this Aspose.Words for .NET 20.7 update and this Aspose.Words for Java 20.7 update.