Apose.total_for_cpp_windows_26.6.0
Platform: Windows 11
I saw my issue with that configuration, then I overlayed
Aspose.Cell-for-Cpp-26.7-windows and Aspose.PDF.Cpp.26.7 and continue to see my issue
Platform: Windows 11
Issue:
My issue is when I convert the attached Excel document for conversion to PDF, the resulting PDF is wrong.
In this Excel file we use an installed Aptos Narrows Font and an Arial font. When we convert to PDF the resulting PDF does not have a Aptos Narrow font but a substitute font is used, SimSn-ExtB
Lastly, I did the same test but i used a Word document and it converted correctly. Its only the Excel document with the Aptos Narrows font that is getting substituted.
So if it works for Word, I must have my machine configured correctly.
Thank you for the additional information and for confirming that the font is correctly installed on your system. Your observation regarding the successful conversion in Word versus the substitution in Excel is a valuable detail for our investigation.
We have updated the internal ticket with these new findings, including the fact that the issue persists on our online conversion tools. This suggests the behavior may be specific to how the Aspose.Cells rendering engine handles this particular font family compared to other formats.
The development team is currently investigating why the substitution is occurring despite the font being available in the system directory. We will continue to look into this and provide you with an update as soon as we have more information or a resolution.
@wlaube
Hi,
Please use the following code to verify whether the font has loaded successfully. If it fails to load, please send us your font file; this will help us troubleshoot the issue. bool b = FontConfigs::IsFontAvailable(u"Aptos Narrow");
Typically, if your font is installed in the c:\windows\fonts directory, this code will return true.
So the first answer is b was true, font was installed.
The second thing is, I don’t know what I’ve changed since I submitted this, but things are working. The Aptos Narrow font is being applied to the output PDF file correctly.
And I ran with and without the IsFontAvailable change and things are working so we can close this issue.