But it doesn't hurt to have such a script...
We need to inform the users, that we provide default-fonts for all systems from date x.
And we should also point out that the font should be chosen if users are thinking about or relying on cross-system data exchange.Do we need to adjust the Elements-Collection, too?
This could be done with a small script, but we would need to agree on which fonts to replace with which others:
Sans Serif or Arial --> Liberation Sans
Serif or Times New Roman --> Liberation Serif
MS Shell Dlg --> ???
It makes sense to ensure cross-system compatibility by providing a default free font that behaves consistently across Linux, MacOS, and Windows. Using Liberation Sans as the default is a solid choice since it closely matches Arial while being open-source.
Regarding implementation, hardcoding the default font settings in generalconfigurationpage.* seems like the simplest and most reliable approach. However, having an optional script to modify registry settings for Windows users could still be useful, especially for those who prefer manual control over font settings.
Additionally, updating the Elements Collection to align with the new defaults is a good idea to prevent inconsistencies. Defining clear replacement rules (e.g., Sans Serif → Liberation Sans, Times New Roman → Liberation Serif) would help standardize the transition.
Would it make sense to include these font settings in a configuration file instead, so users can override them without modifying the registry or code directly?