Comment 33 for bug 94282

Thank you Magi, for the information you provided. :)

This morning I finally get Qt working with font substitution, however still not conforming to the Fontconfig settings automatically as GNOME does. I found that there's no "qt3-qtconfig" package installed on my system, only "qt4-qtconfig"; and since Kubuntu is still using KDE 3 mainly, I guess all those applications, including kicker, can only be configured with qtconfig of respective version, so that's why I have customized in "qt4-qtconfig" but without success. I don't know if this is the result of my installing kde-desktop on Ubuntu, not installing Kubuntu itself directly, so that I lack qt3-qtconfig by default.

So now I can get Purisa, Nimbus, Chandas, or any other English fonts to mobilize fallback fonts such as Microsoft JhengHei now. But even with qtconfig, we still have to set fallback information to "each" font which we'd like to be substituted. I remember that with Fontconfig files, only setting preferences for Sans Serif, Serif, and Monospace would do all the work, and GNOME would apply settings of these three generic font family to all other specific fonts, so that any fonts in the list can mobilize Chinese fonts automatically. And I'm still not satisfied with the way KDE and Qt behaves...

As of the Ubuntu forum of China (zh-CN), I appreciate that it has a section just for Chinese language support, but searching with "kde OR kubuntu" didn't yield many results relating to the fontconfig issue in KDE. Anyway, thank you for showing me the way!