Fonts usage in Aspose.Words on Windows

Aspose.Words Product Family
1

I want to clarify a few things about using non-standard fonts on Windows.

  1. The documentation says that only the default instance is supported for ‘OpenType Font Variations’.
    I attached a sample of the font.
    a) Is that the case for it?
    b) Are there any plans for supporting other fonts in a package?

  2. Is there a list of locations from where the fonts are loaded by the library?
    I know some fonts can be located in the following locations:
    C:\Users<user>\AppData\Local\Microsoft\FontCache\4\CloudFonts
    C:\Users<user>\AppData\Local\Microsoft\Windows\Fonts
    a) Does Aspose is expected to use these?
    b) Are there any plans to do it?

test42.zip (204.2 KB)

2

@licenses

Could you please specify which non-standard fonts you are referring to and clarify your questions regarding the support for these fonts in Aspose.Words?

3

@licenses

1.a. Yes, this statement is applicable to the attached font.

1174×278 12.3 KB

1.b. Yes, this feature request is logged as WORDSNET-18994. I linked your topic to this feature request. We will keep you updated and let you know once it is supported.

2.a. On Windows Aspose.Words by default looks for fonts in C:\Windows\Fonts folder. In addition, on Windows platform we also check the registry for font files. You are free to add additional font location. Please see our documentation to learn how to specify fonts location:
https://docs.aspose.com/words/net/specifying-truetype-fonts-location/

2.b. You already can specify additional font sources. So no need to change this behavior in Aspose.Words.

4

Thanks, this answers my questions.

1 Like
5

I have found an issue with ‘Segoe UI Emoji’ font on Windows 11 during conversion to *.pdf format.
IWarningCallback returns the next message: Font ‘Segoe UI Emoji’ has not been found. Using ‘Fanwood’ font instead. Reason: first available font.

The file (SEGUIEMJ.TTF) is present in the Font directory for both Windows 10 and 11, but the versions are different - 1.29 and 1.51 respectively.
I tried to load those fonts manually on Windows 10 and 11, but the result is the same.
I attached the document and the fonts.

Does Aspose.Words supposed to support this font or the changes in the new version has made it into some unsupported type of font?

Code sample:

var doc = new Document(inPath);

doc.WarningCallback = new HandleDocumentWarnings();
FontSettings.DefaultInstance.SetFontsSources(new FontSourceBase[] {new FolderFontSource(fontDir, false)});

var optPdf = new PdfSaveOptions();
doc.Save(fontDir + "test.pdf", optPdf);

I use Aspose.Words.dll 25.3.0.0.
test43.zip (7.3 MB)

6

@licenses
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-28017

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

PS: It looks like the problem occurs only with newer 1.51 version of Segoe UI Emoji font. If put only 1.29 version of the font into the fonts folder the problem does not occur.

7

Yes, there is no problem with 1.29. I attached it for comparison.
Windows 10 has version 1.29 and it is Ok.
Windows 11 has version 1.51 and there is an issue.

1 Like