Fonts Loading in memory

Hi , we are using Aspose to convert PDF to PDFA 3 B Format
Note We are not using System Fonts at all

We are Settting the Font Source explicitly as
FontRepositery.Source.Add(new Aspsoe.Pdf.Text.FolderFontSource(@“D:\Fonts”))

where D:\Fonts contains 600 Fonts.

Now the Question is after executing FontRepositery.Source.Add(new Aspsoe.Pdf.Text.FolderFontSource(@“D:\Fonts”))

line, will Aspose Load all the 600 Font in its memory or it Loads only those fonts from the Source which are needed by Aspose for the Conversion of Document (Assume document is having 5 fonts in it)?

Please Note : We want to Embed Font in Document, we dont want to Just EmbedSubset ,

Please Note your reply will play a very important role in our architecual decision so please be Precise while replying. As i tried to Google few things around it and there is no precise reply for the same.

@GayatriNaik

Can you please clarify if you are asking whether Aspose loads all fonts into memory or only the fonts required for the specific document conversion? Additionally, please specify the version of Aspose.PDF you are using.

We also have Japanese font in folder so we dont know which all fonts can be used in PDF document as this Documents are Randomly send to us. we dont want to set the Source Each Font by Font ie one by one , we want to Set the Font Source only once it main folder location only. and not specific Font Individual path eg.Arial.tiff path

@GayatriNaik

No, the API does not load all fonts into memory from the directory. The fonts are loaded on demand when assigning in the PDF documents. If you specify the fonts path, API will search the fonts in that directory to use it for processing the PDF documents.

So assuming my D:\Fonts has 600 Fonts and my PDF need only arial Font ie 1 font then

FontRepositery.Source.Add(new Aspsoe.Pdf.Text.FolderFontSource(@“D:\Fonts”))

Then Aspose will Load only 1 Font and not all 600 fonts internally when it need for conversion Am i right ??

@asad.ali Please reply

@GayatriNaik

Yes, you are right. The API will only load Arial font at the time of PDF generation instead of loading all 600 fonts from the directory.