Do not ignore missing default conf.d
Submitted by Jehan Pagès
Assigned to fon..@..op.org
This is a follow-up of bug 69836. A very very minor improvement. Basically I think that the conf.d/ default configuration folder should not be ignored if missing in the default setup.
We had various font-related bugs on the released GIMP 2.8.6 for Windows, because the conf.d was not found, and it was hard to diagnose because not much feedback from fontconfig. The configuration issue has now been fixed with bug 69836 (thanks for that!), but if another similar configuration issue was to arise again, it would be nice to have default feedback.
I understand that the configuration files can be considered an "optional" thing for some advanced users, and these users would likely not use, or have their own files. But for these advanced users, they would modify on purpose the fonts.conf file anyway. On the other hand the very basic user, which just install fontconfig, does not touch much, if at all the fonts.conf, and expects it to work like it always did, this one expects the conf.d/ configuration directory to exist. For this user, I would say that the conf.d/ folder and its contents is not considered an optional thing at all, but a major feature (for instance in GIMP, the default conf.d allows to simulate bold/italic typefaces for fonts which don't have these features by default, and users were considering that GIMP was bugged on Windows because of this issue: https://bugzilla.gnome.org/show_bug.cgi?id=708110).
This is why I propose this small patch to use ignore-missing="no". Because when such a configuration issue, the "default" fonts.conf should warn the user there is an issue.