Open RJVB opened 8 years ago
bohoomil
commented
8 years ago We are using the Xft settings file because certain apps simply use these variables. They cannot be hard-coded because originally they belong neither to freetype-infinality nor fontconfig.
RJVB
commented
8 years ago Sorry, I don't get it. What (kind of) apps are we talking about, and what do they do with those variables? As to hardcoding default values: those variables have to be used in fontconfig and/or freetype source code, right? If they can be set to sensible, global defaults in a script, why would it be impossible or wrong to use that default in the code for (env.) variables that are not defined because the script wasn't sourced?
R
On 30 Mar 2016, at 02:03, bohoomil notifications@github.com wrote:
We are using the Xft settings file because certain apps simply use these variables. They cannot be hard-coded because originally they belong neither to freetype-infinality nor fontconfig.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub
bohoomil
commented
8 years ago Apps depending on libxft and variables set via .Xresources, which basically means Gtk+ and stuff (Firefox for example).
those variables have to be used in fontconfig and/or freetype source code, right?
Nope. Again, it's libxft that's responsible for rendering parameters. See man Xft for more info.
Does xft-settings.sh in its current version actually change anything to the fontconfig defaults? If it does, I'd suggest aligning with the current freetype-infinality approach, in which the "optimal" settings are provided as hardcoded defaults so that users aren't required to call any configuration scripts.
My impression from looking at the fontconfig code is that xft-settings.sh indeed just "confirms" (some of) the defaults, but that code doesn't exactly excel in clarity.