Noto fonts screw my system, please stop forcing fonts upon me!
Johan Ouwerkerk
jm.ouwerkerk at gmail.com
Thu Dec 17 22:45:20 UTC 2015
> It is a very hard forced dependency on that font.
At build time, yes. At run time, you can simply reconfigure your
preferences in System Settings, uninstall both Oxygen and Noto
completely (with package manager) and still continue to use Plasma.
On Thu, Dec 17, 2015 at 11:09 PM, Mark Gaiser <markg85 at gmail.com> wrote:
>
>
> On Thu, Dec 17, 2015 at 10:09 PM, Eike Hein <hein at kde.org> wrote:
>>
>>
>> Hi Mark,
>>
>> I think you might not be entirely clear on what we're doing.
>
>
> Perhaps.
>
>>
>>
>> It's not a forced dependency/font, it's a default font setting
>> which compells distro packagers to pull the font packages in as
>> dependency. However you can change the font in System Settings
>> to your liking.
>
>
> No, that is just not the case. The CMake line for frameworkintegration
> states:
> feature_summary(WHAT ALL FATAL_ON_MISSING_REQUIRED_PACKAGES)
> message("** frameworkintegration uses Noto Sans
> (https://www.google.com/get/noto/) and Oxygen Mono
> (http://download.kde.org/stable/plasma/5.4.0/oxygen-fonts-5.4.0.tar.xz)
> fonts, ensure these are installed for use at runtime")
>
> It is a very hard forced dependency on that font.
>
>>
>> As for why Noto: It's designed for screens (both low and high
>> ppi), very high-quality and has very broad character set support,
>> enabling a high aesthetic standard consistently across a wide
>> variety of locales for the first time on Linux. In particular
>> in scenarios of mixed character set text this is a huge impro-
>> vement on the earlier situation (where glyph substitution often
>> puts typefaces that don't fit next to each other). It's also
>> under active ongoing development and has significant resources
>> behind it, and some of the leading type foundries around the
>> planet.
>
>
> What you say might be true and might be the goal of that font.
> But it is unusable for me at this moment and i'm not going to make bug
> reports about that.
>
> It is the google font (noto) with the google browser (chromium) that mainly
> screws things up completely.
>
> It's either heavily bugged or not ready to be used.
> Either case should be sufficient reason to not use it in Plasma 5.
>
>>
>>
>> As for your link to the website wrt/ line spacing, please
>> note that the style sheet of that website forces a line height
>> of 1.71429 (1.0 being normal), i.e. the line height there isn't
>> representative of normal text layout using Noto.
>
>
> You are wrong.
> The line height might be what you said, but what you see isn't a font
> rendered by chrome. The link i gave earlier
> (https://www.google.com/get/noto/#sans-lgc) shows the fonts rendered in a
> SVG image. The css line height has nothing to do with that. So what you see
> in that image is how it will look if you use that font. And that is just
> completely useless for desktop usage. It's fine to use that font in for
> example designs made in gimp or photoshop.. But not as desktop font!
>
>>
>>
>>
>> > Best regards,
>> > Mark
>>
>> Cheers,
>> Eike
>> _______________________________________________
>> Plasma-devel mailing list
>> Plasma-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
More information about the Plasma-devel
mailing list