On Thu, Aug 4, 2016 at 2:43 PM, Takashi Iwai
Well, it's a problem of Unicode in general. The issue may happen no matter whether ttc or not. Japanese is chosen just because of the alphabet order in this case.
Yes...it's not ttc or ttf, but "one" ttc or "many" ttcs. If we use separated ttcs, you can install Chinese variant and see Chinese right if you see Chinese not displayed under any locale. But if we use one ttc, you will not see Chinese right even if you have installed Chinese variant in English (which is not covered by the tweak and should not be covered) Because the locale-based tweak and the unicode problem. So I think this might be a shortcoming for this topic. Because users will not get the behavior they want in some cases.
If the web page specifies properly the language attribute, the rendering should be fine. But most of web pages don't do the right thing :)
Most of the web pages will only specify "sans-serif" and let the system decide. The language attribute is not possible at all, because any web page may have something English...A good part of fontconfig is that you can use a font to display English and fallback to the other when CJK characters come out. This technology is commonly used in Windows/Mac/Linux... Marguerite -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org