I just experienced the same problem and was about to report a bug for it, but it seems I wasn't the first. The issue is that fontconfig has standard aliases "sans", "serif", and "monospace" which applications should use to get the user's preferred font in each of these 3 families. A good fontconfig setup will have a series of fallbacks for each of these 3 aliases containing appropriate fonts for all scripts and languages, so it is highly advised to use them to ensure support for non-Latin scripts. Moreover, various websites use these font names as the final fallback in their CSS.
The ttf-georgewilliams package installs a font named Monospace, and this conflicts with the fontconfig alias. Fontconfig aliases are only used when an actual font by that name does not exist. Aside from the 3 standard aliases, the purpose of these aliases is to allow users to configure fallbacks for specific font names in case that font isn't installed (very useful workaround for documents that ask for proprietary fonts), so I suppose it was considered preferable to always use the "real font" if it exists. But in the case of "Monospace", this is not the "real font" but a very very ugly and incomplete font that happens to be in the monospace style. Please rename this font or simply remove it. I don't think anyone would miss it... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
