By default, both GDI+ anti-aliased drawing and PDF file generation using our libraries did lack of font-fallback implementation.
If some of the characters in a string are not supported in a requested font, they were drawn as square symbols on the GDI+ canvas or the PDF content.
The font-fallback mechanism implemented will use a third-party font (Arial Unicode MS by default, which is installed with Microsoft Office), for any glyph that are missing when rendering the content. Of course, for PDF generation, you are able to embed the font within the generated file (this is by the way mandatory for PDF/A-1 format).
Both of these new features are handled by the SQlite3Pages
unit, i.e. for report anti-aliased drawing preview and PDF generation.
By the way, the TGDIPages class itself (the one used for
report generation from
code) now handles by default Unicode text, even with Delphi
versions prior to 2009 (via the SynUnicode string type, which maps
WideString before Delphi 2009, then UnicodeString
starting with Delphi 2009). Does make sense with such
a font-fallback mechanism.
