Skip to content

Conversation

@pinwhell
Copy link

Refactored font-family property to use a list of font families instead of a single string. Updated related interfaces and logic to iterate through font families and select the first available font. Adjusted tests to use multiple font families in style definitions.

Refactored font-family property to use StringList instead of String, allowing for multiple font families to be specified and tried in order. Updated ComputeFontFamily and related interfaces to handle lists, and added logic to FontEngineInterface to select the first available font from a list. Updated tests to use multiple font families.
@mikke89 mikke89 added the enhancement New feature or request label Nov 1, 2025
@mikke89
Copy link
Owner

mikke89 commented Nov 1, 2025

Hi, and thanks for making a pull request!

Can you elaborate on the motivation behind this change?

The assumption generally for the library is that users are in control of their environment. This includes being aware of which fonts they load and making available. Thus, a missing font face is considered an error.

There has been some discussion around multiple font families earlier, here in the context of fallback fonts: #500

@pinwhell
Copy link
Author

pinwhell commented Nov 1, 2025

Honestly.. i tried the Syntax.. font-family Font1, Font2; and i saw it didn't work so i thought it was cool to simply implement it.. but now that i look closely at #500 it seems like a philosophy mismatch

@pinwhell pinwhell closed this Nov 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants