http://bugzilla.opensuse.org/show_bug.cgi?id=1032849 http://bugzilla.opensuse.org/show_bug.cgi?id=1032849#c3 Marguerite Su <i@marguerite.su> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Marguerite Su <i@marguerite.su> --- Hi, Jan, Adobe Source Han and Google Noto Sans CJK are the same thing. This typeface is a joint effect by the two companies. The only difference is: Adobe uses Source Sans Pro for the Latin part, while Google wants to use Roboto/Noto Sans. The CJK part of this typeface is designed to work with both Source Sans Pro and Noto Sans from the beginning. https://blogs.adobe.com/CCJKType/2017/04/source-han-serif-history-developmen... https://blog.typekit.com/2014/07/15/introducing-source-han-sans/ And Google wants you to prefix with Noto Sans to override the Source Sans Pro part (the Latin part to be specific) That's how the URL you pasted reads. The Latin part is just Adobe Source Sans Pro in both Noto Sans CJK and Adobe Source Han. and their CJK part are the same too. Google just renames it without changing anything. AND: openSUSE M17N maintainers (or Petr to be specific) have a fonts-config package, which contains all the system fontconfig configurations. In that package, we'll override both. That is, neither Sources Sans Pro or Noto Sans will be used for displaying Latin. Every Latin on openSUSE is displayed with the same font (even on CJK systems) that we choose by ourselves. So considering that, this bug is valid. Because: 1. Google used Adobe Source Han exactly, just renamed to Noto Sans CJK. 2. Google prefixed it with Noto Sans to get what they want. it's a workaround. the font is still the same. Personally I think the best way to fix this is to strip CJK part entirely from the packages mentioned in this report. And let Google Noto provides it (because the later has a full coverage right now, this will save you a lot of work). Greetings Marguerite -- You are receiving this mail because: You are on the CC list for the bug.