Skip to content

Cross-Platform Font Discovery Is Documented Incorrectly - #800

Open
dessyordanova wants to merge 1 commit into
masterfrom
dess-content-gap-fill
Open

Cross-Platform Font Discovery Is Documented Incorrectly#800
dessyordanova wants to merge 1 commit into
masterfrom
dess-content-gap-fill

Conversation

@dessyordanova

Copy link
Copy Markdown
Collaborator

Priority: Critical
Confidence: 10

Missing Functionality: The implementation automatically installs SystemFontsFontsProvider when no custom provider is configured. It discovers fonts across Windows, Linux, macOS, iOS, and Android.

Evidence Found in Code:

  • Documents/Fixed/Core/Extensibility/FixedExtensibilityManager.cs
  • Documents/Fixed/Core/Extensibility/SystemFontsFontsProvider.cs

Current Documentation Status: Outdated. The cross-platform font documentation implies that applications must always provide a custom font provider.

Recommended Documentation: Explain automatic system-font discovery, supported platforms, discovery paths, fallback behavior, and when an application still needs a custom provider.

Business/User Impact: Users may add unnecessary configuration or believe cross-platform PDF generation is unsupported without custom font code.

Confidence Score: 10

@dessyordanova dessyordanova self-assigned this Aug 7, 2026
@dessyordanova
dessyordanova requested a review from YoanKar August 7, 2026 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant