Thanks for your patience.
Regarding earlier logged ticket (PDFNET-39227), setting font encoding is not recommended and we cannot implement this in our API. Please note that PDF document can include different types of fonts and only one kind of these fonts - named composite or Type0 fonts can have this encoding (i.e IDENTITY). Each font have its own identity set which is compatible with that font and if we change this IDENTITY, the PDF document will get corrupted.
Current custom font substitution in Aspose.PDF (using
in a declarative manner. It changes original font name with a new font name in PDF document, so Adobe Acrobat or another PDF viewer will use another font to show text. Font encoding and other data related to font are not changed.This declarative font substitution possibly can cause problems, when new font is not fully compatible with original font.
But change (set) of font encoding will not solve these problems. Serious change of font data and document content is needed to solve them. However, in case you face any font substitution issue or text is not rendering correctly inside your PDF, you may please share your sample PDF document and code snippet with us. We will investigate the scenario accordingly and share our feedback with you.