Conversation
|
@kjarosh does this seem reasonable? |
|
Thanks @wezm for the fixes, I appreciate it! I think it's a good move to expose However, I'm wondering if there's a reason those calls are separate in fontconfig. I'm not experienced enough with fontconfig to say it for sure, but it's possible there are some use cases which require not calling substitutions before sorting or matching fonts. Edit: or maybe it's about selecting a different config for substitutions or using |
I'm not sure if there are such cases either, but since this just brings |
default_substituteandconfig_substituteinsort_fonts.sort_fontsa method ofPattern, which makes it consistent withfont_match.default_substituteandconfig_substitutein public API in case they are needed in other situations.Fixes #45