Provide Option to Turn Off Checking AltName from FontInfo


#1

I can understand the reasons behind prioritizing altName above Aspose’s font substitution logic, but agree with @workiva_jackson that this has unintended consequences: Word’s “w:name” field doesn’t always contain the “exact font name match” according to Aspose. The previous fallback logic was reliably able to match accurately.

Another way to frame this is that Aspose’s “exact font name match” isn’t working well enough, and some of the font substitution logic should be incorporated into it.


Font Substitution Issue in Words for Java version 19.2+
#2

@justinlindh,

We have logged this requirement in our issue tracking system. Your ticket number is WORDSNET-19524. We will further look into the details of this requirement and will keep you updated on the status of the linked issue. We apologize for any inconvenience.


#3

@justinlindh,

Regarding WORDSNET-19524, for this particular scenario, there is an easy workaround i.e. you can just clear the AltName field for each FontInfo in Document.FontInfos before the rendering. Could you please check and let us know if this will be acceptable for you? Thanks for your cooperation.