CODEWITHSUNDEEP
c#pdfxsl-foapache-fopwingdings
Bunkai.Satori
Bunkai.Satori

Reputation: 4758

Apache FOP for .NET Core (FOP.NetCore v. 3.0): Wingdings 2/3 not found

Our organization switched to using C# Apache FOP.NetCore 3.0 .NET library to generate PDF documents recently. Shortly after the switch, we discovered that we can not use "Wingdings 2" and "Wingdings 3" TTFs in the generated PDF documents. However, we can use "Wingdings" (the "first" TTF version).

We do not get any error message, but the generated PDFs do not contain any Wingdings 2 / 3 symbols. Instead, in place of Wingdings 2 it uses empty boxes.

I tried multiple ways to define "Wingdings 2" font-family using XSL-FO. Few of the examples:

In the XML Files, which are used to define PDF documents using XSL-FO (XSL Formatting Objects), we can without problems use Wingdings TTF (but not Wingings 2 or 3).

Wingdings 2 / 3 TTFs are properly installed in my OS (Windows 10), and I can use them in another applications (ex. MS Word 2019).

Have you had similar experience and would you know, please, how to properly specify "Wingdings 2" string to appear in a .pdf file using XSL-FO? Thanks, many times.

I expected seeing characters specific to Wingdings 2 in the generated .pdf document. Instead I got small rectangles for each character, meaning, the defined TTF/Font-Family has not been found.

Upvotes: 0

Views: 62

Answers (0)

Related Questions