Basically, when I try to use FontAwesome glyphs with QuestPDF, I get unexpected characters. I force FontAwesome to work by using the Skia canvas renderer and manually drawing the glyph's SVG, but this is less than ideal because I have to use
Unconstrained()
Unconstrained()
to silence the overflow warning and I have to scale and position the glyph manually.
The fonts are in fact installed and I can use them (e.g. in Word), but it's behaving like the font family is not being applied to the text. Any thoughts on what I might be missing and/or doing weird that's causing this behavior?
Below is a sample I have set up. Don't mind the color differences. Column 1 draws the glyph with the canvas renderer. Column 2 uses a text element with the unicode of the same icon with its font family set to Font Awesome 6 Pro Column 3 is a text element with the letter M.
Hi all, I'm trying to get QuestPDF to work with FontAwesome. I am running on Windows 10 Enterprise and targeting .NET 6. I have installed the FontAwesome OTF files and confirmed that they w...