diff options
| author | Matthias Clasen <mclasen@redhat.com> | 2022-06-26 11:13:01 -0400 |
|---|---|---|
| committer | Matthias Clasen <mclasen@redhat.com> | 2022-07-04 11:17:28 -0400 |
| commit | f51d318abbb9e67fd362129a2f2af81e77b9d691 (patch) | |
| tree | e41755078c9ed596c23b9b2e44c1954770f86355 /docs/migrating.md | |
| parent | b29fdef4cc5bf08bc89066b36907ceddc0657edf (diff) | |
| download | pango-f51d318abbb9e67fd362129a2f2af81e77b9d691.tar.gz | |
Add defines for native fontmaps
Add PANGO_HAS_FC/CORE_TEXT/DIRECT_WRITE_FONTMAP macros
to let apps check for the presence of native fontmaps.
Diffstat (limited to 'docs/migrating.md')
| -rw-r--r-- | docs/migrating.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/migrating.md b/docs/migrating.md index fbd0bddb..7c1e3b37 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -64,7 +64,15 @@ the `pangocairo.h` header, and use the APIs that are declared in it. There is still a `pango2cairo.pc` file, if you want to be explicit in your build configuration about requiring cairo support. If you want to handle the possible absence of cairo support at runtime, you can check the -[const@Pango2.RENDERING_CAIRO] macro before including `pangocairo.h`. +`PANGO2_HAS_CAIRO` macro before including `pangocairo.h`. + +The native fontmap implementations provide their own headers: +`pangofc-fontmap.h`, `pangocoretext-fontmap.h` and `pangodwrite-fontmap.h`. +If you want to check for the available fontmaps implementations +at runtime (even though they are entirely determined by the platform you +are running on, currently), you can check the `PANGO2_HAS_FC_FONTMAP`, +`PANGO2_HAS_CORE_TEXT_FONTMAP` and `PANGO2_HAS_DIRECT_WRITE_FONTMAP` macros +before including the corresponding header file. ### PangoFontMap changes |