fcft_capabilities(3)
π fcft_capabilities(3) β the fcft girlies' capability check
okay so this page lives in the fcft manual, and it's literally the "what can this build even do" page. no cap, it's short and it slays.
β¨ NAME β¨
fcft_capabilities β the optional library capabilities that are actually available, bestie π
π¦ SYNOPSIS π¦
#include <fcft/fcft.h>
enum fcft_capabilities fcft_capabilities(void);
πΈ DESCRIPTION πΈ
fcft_capabilities() returns a bitmask of the optional library capabilities that are enabled π
enum fcft_capabilities {
FCFT_CAPABILITY_GRAPHEME_SHAPING = 0x1, /* Since 2.3.0 */
FCFT_CAPABILITY_TEXT_RUN_SHAPING = 0x2, /* Since 2.4.0 */
FCFT_CAPABILITY_SVG = 0x4, /* Since 3.1.0 */
};
like, it's giving "vibe check for your build flags" fr fr π«Ά
π FCFT_CAPABILITY_GRAPHEME_SHAPING π
fcft can do grapheme shaping (using HarfBuzz), and fcft_grapheme_rasterize() can be expected to return non-NULL. iconic behavior, honestly πβ¨
π₯ FCFT_CAPABILITY_TEXT_RUN_SHAPING π₯
fcft can do text-run shaping (using HarfBuzz), and fcft_text_run_rasterize() can be expected to return non-NULL. yes bestie, the text runs are shaped π
π§ FCFT_CAPABILITY_SVG π§
fcft can rasterize glyphs from OT-SVG fonts. little SVG glow-up, we love to see it π
π SEE ALSO π
fcft_grapheme_glyph_rasterize(), fcft_text_run_rasterize()
ngl, if a capability bit isn't set, don't go expecting that function to hand you a non-NULL β that's the whole point of checking. vibe check first, code second π
β mwah π this page is from fcft 3.3.3, dated 2026-04-09 β go off, little manual page, you ate ππ
π¦ where this page comes from
- alpine 3.24: fcft-doc 3.3.3-r0 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms