Phase 4.1: cross-platform font spike - #34
Merged
Merged
Conversation
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #27.
Spike evidence + prototype adapter (Linux verified; macOS/Windows stubs documented):
src/fonts.rs:resolve_os_monospace()via fontconfigfc-matchon Linux;Nonestubs elsewhere. 6 spike tests at the shaping seam.Family::Monospacefrom its own first monospaced face and ignores fontdb's generic remap — the editor must use explicitFamilyOwned::Name(Phase 4.5).docs/font-delivery-research.md: spike verification section + pending cross-platform list (manual cells deferred to Phase 4.7 on physical machines).CI note: OS-dependent tests are
#[cfg(target_os = \linux\)]; the remap test runs on all three platforms. macOS/Windows adapter behavior remains unverified by design until Phase 4.5.