[Fontconfig] 'loading' vs. 'scanning' config files

[Akira TAGOH]

Hi,

That is to get a config file list through FcConfigFileInfoIter* and
see what it is for and if it is enabled or not. enabling a config
directly through API isn't yet supported but that can be done with
some manual work even now. one just needs to reload a FcConfig after
updating a symlink of config files.

Hope this helps,

On Tue, Dec 13, 2022 at 9:44 PM Werner LEMBERG <wl at gnu.org> wrote:
>
>
> If I say
>
> ```
> FC_DEBUG=1024 fc-list
> ```
>
> I get
>
> ```
> Loading config file from /etc/fonts/fonts.conf
> Scanning config dir /etc/fonts/conf.d
> Loading config file from /etc/fonts/conf.d/10-group-tt-hinted-fonts.conf
> Loading config file from /etc/fonts/conf.d/10-group-tt-hinted-fonts.conf done
> ...
> Loading config file from /etc/fonts/conf.d/90-synthetic.conf done
> Loading config file from /etc/fonts/fonts.conf done
> Scanning config dir /usr/share/fontconfig/conf.avail
> Scanning config file from /usr/share/fontconfig/conf.avail/10-autohint.conf
> Scanning config file from /usr/share/fontconfig/conf.avail/10-autohint.conf done
> ...
> ```
>
> What is the difference between 'loading' and 'scanning'?  And why does
> FontConfig look at all into the `conf.avail` directory, which is
> nowhere specified in a configuration file?
>
>
>     Werner



-- 
Akira TAGOH