Re: Discussion: Porting noto font family to our openSUSE

On Wed, 27 Jul 2016 14:45:39 +0200,
ZhaoQiang wrote:
> 
> Hi, all:
> 
> As we know, openSUSE leap 42.1 locale zh_* has changed the default
> fonts to google-noto, and make Chinese openSUSE's font render much
> beautiful.
> 
> As the description in wiki page:
> Noto is a font family designed to cover all the scripts encoded in the
> Unicode standard. It is designed with the goal of achieving visual
> harmony (e.g., compatible heights and stroke thicknesses) across
> multiple languages/scripts. Commissioned by Google, the font is
> licensed under the SIL Open Font License. Until September 2015, the
> fonts were under the Apache License 2.0.
> 
> I propose to port noto font family to other language to openSUSE
> desktop as default font.
> But I'm wondering, is there any country or area improper to use it?

For a bit more information: this inquiry came from a bug report for
SLED12-SP2.

Yes, we have already google-noto-fonts and noto-sans-cjk-fonts
packages.  However, noto-sans-cjk-fonts has the line

  Provides:       locale(zh_CN;zh_SG;zh_TW;zh_HK;zh_MO)

thus only Chinese locales will install this as default.  For making
noto-sans-cjk font to be installed automatically on Japanese and
Korean locales, we'd need to put "ja" and "ko" there.

However, there is one pintfall: noto sans CJK fonts are always
prepended to the list of "sans" aliases, so once when this package is
installed, this will be used in prior to other fonts as a
system-default font.

Also note that the Provides() in the spec file plays a role as
"recommends" (or more accurately, other way round -- the package is
recommended on the corresponding running locale).  Hence, adding to
Provides() shouldn't influence on the already installed system, unless
you do zypper install-recommends or such.

So, if anyone has a strong objection against adding ja and ko locales
to Provides() of noto-sans-cjk -- so that this package will *not* be
drug onto a fresh installation, please speak up.

I don't guess there won't be so many people actually against it, but
we'd like to have a consensus before going forward.


thanks,

Takashi
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]