We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Different font substitution in versions 17.4 and 17.2 that totally changes document structure

In case if font ‘Tw Cen MT’ is not presented on the server, Aspose in version 17.2 substituted to ‘Times New Roman’, but in version 17.4 it substituted with ‘Lucida Sans Unicode’, that totally change document structure

1. Open attached ‘RDSA_Master_31.2.docx’ document in Word.
3. Notice that font is ‘Tw Cen M’.
4. Convert this document with Aspose.Word version 17.2 and 17.4 and notice the difference between font substitution in converted html.

Actual result:
In Aspose.Word version 17.2 font ‘Tw Cen MT’ was substituted to ‘Times New Roman’(and this is ok for us).
But in version 17.4 ‘Tw Cen MT’ is substituted to ‘Lucida Sans Unicode’.
So we do not have stability in font substitution from version to version.

Expected result:
‘Times New Roman’ is expected to be substituted instead of ‘Tw Cen MT’ in 17.4.
Substituted font is expected to be stabile from version to version.

Why substituted font is changed? which logic do you use to choose substitution font? Will it be changing from version to version?

Best regards,
Olga Kyrychuk

Hi Olga,

Thanks for your inquriy. Please check Public API and Backward Incompatible changes section in Release notes of Aspose.Words for .NET 17.3.0. We have improved font substitution mechanism in that version. So you are getting different results as compared to 17.2.

Best Regards,