Hello. I think I already know the answer, but wanted to see if I could get confirmation. I am using an older version of Aspose Total and doing some document conversions from Word to PDF along with some other processing of the document. I think the latest supported version of my license was 19.8 and the document post conversion just shows up as boxes, so I believe this may have been the issue with Indic languages that was addressed with WORDSNET-13503 that was addressed in the Aspose Words 20.8 Release. I had a similar issue with some Cambodian documents, but was able to address by adding the Khymer TTF font to the server. I did add the Arial Unicode MS font to the server, but still not resolving, so thinking it is an issue resolving the fonts within that family that was addressed in 13503. Is it possible to upload both the base doc and the failed conversion to confirm that 20.8 or later addresses the issue. If this was indeed fixed with that, I guess our next step would be to purchase a new license to get the newer release which handles this. Thanks
Can you please provide the specific details of the document you are trying to convert and the exact error message or issue you are encountering with the Arial Unicode MS font?
Attached are both the base document and the conversion which shows that the font family is not being properly rendered.
E__iRISDocs_Converted_Consent_120272_dl556.pdf (1.2 MB)
Consent_120272.docx (57.1 KB)
@dlaskey I tested conversion of your document using the latest 25.3 version of Aspose.Words and the output document looks good:
out.pdf (159.4 KB)
Also, to properly render your document it is required to enable open type featrues:
Document doc = new Document(@"C:\Temp\in.docx");
doc.LayoutOptions.TextShaperFactory = Aspose.Words.Shaping.HarfBuzz.HarfBuzzTextShaperFactory.Instance;
doc.Save(@"C:\Temp\out_HarfBuzz.pdf");
out_HarfBuzz.pdf (195.9 KB)
A follow up question for you. Is it possible to get a temporary/trial license to be able to test against the latest version locally? While it is great that the 25.3 version of Aspose.Words is able to handle the font, I want to make sure the rest of our automated document processing still functions.
On the Word side, we add in headers as well as footers including adding a table in the footer.
On the PDF side, we also will do processing on the header, including adding some textboxes and javascript (copies info entered in the page 1 Textboxes to all pages in the PDF. Textstamps and other similar are performed as well
Sure, if you would like to test new version of Aspose.Words without evaluation version limitations, you can request a free 30-days temporary license .
So I have been doing testing as well as others, and in general the latest version resolves the issues we were encountering with the 19.6 version, however, we did run into some issues when processing areas that had lines for signatures, etc. and some formatting issues. Please see the attached base document as well as what we were getting for a converted PDF. I was wondering if there were some additional settings or parameters I need to add to preserve some of this kind of formatting. Thanks
20-272 AM 528723 Main ICF_Arabic (4).docx (105.7 KB)
@dlaskey Unfortunately, I cannot reproduce the problem on my side. Also, the attached DOCX document does not match the provided screenshot. In DOCX document there are 28 pages, on the screenshot there are 13 pages. Could you please make sure you have attach the correct document? Also, please attach PDF document produced on your side.
A post was split to a new topic: Powerpoint in arabic to html and its not always aligned as it shown in the powerpoint