The various fontconfig.properties files on windows say

dialog.plain.2=WingDings,SYMBOL_CHARSET

But the font is called "Wingdings" on my XP system.

This caused some code that was expecting to find WingDings to unnecessarily
do extra work (impacting start-up) as it tried a different font search.

That code can be amended to ignore the case but it still desirable to
have the name in the fontconfig file be true to the name of the font.