Products | Support | Email a link to this topic. | Send comments on this topic. | Back to Introduction - All Topics | Help Version 19.0.3.23
|
Leadtools.Pdf Assembly > Leadtools.Pdf Namespace > PDFDocumentPage Class : Fonts Property |
public IList<PDFFont> Fonts {get;}
'Declaration
Public ReadOnly Property Fonts As IList(Of PDFFont)
'Usage
Dim instance As PDFDocumentPage Dim value As IList(Of PDFFont) value = instance.Fonts
public List<PDFFont> getFonts()
public: property IList<PDFFont>^ Fonts { IList<PDFFont>^ get(); }
By default, the Fonts, Annotations, Objects, FormFields, Signatures and Hyperlinks lists are not populated when a new PDFDocument is created and the values of these properties are null. You must call the PDFDocument.ParsePages method to parse the items are you interested in (depending on the PDFParsePagesOptions passed as the options parameter to the method). This is done for performance reasons and to give the user the ability to parse only the objects and pages of interest.
The Fonts list will be populated if PDFParsePagesOptions.Fonts is passed as part of the options parameter to PDFDocument.ParsePages. After this method returns, all the pages parsed will have their Fonts properties populated either with a list of the fonts found in the page or an empty list (with IList<PDFFont>.Count equals to 0).
When parsing is finished, the Objects and Hyperlinks properties will contain a list of the PDFObject and PDFHyperlink items found in the page (if PDFParsePagesOptions.Objects and PDFParsePagesOptions.Hyperlinks was selected). Each of these items contain a PDFTextProperties object that contain the text properties of the item such its font information and color. One of these properties is PDFTextProperties.FontIndex which is the 0-based integer index to the font of the item in the Fonts list.
If PDFParsePagesOptions.Fonts is not passed to PDFDocument.ParsePages, but PDFParsePagesOptions.Objects and PDFParsePagesOptions.Hyperlinks was selected, then the fonts are not parsed and the PDFTextProperties.FontIndex value of any returned object will be 0.
For an example on general parsing of PDF pages, refer to PDFDocumentPage, for an example on drawing the objects of a page on the surface of an image, refer to PDFObject.