|
Bugzilla – Full Text Bug Listing |
| Summary: | Noto-Sans font looks bold and blurry | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Eugene Popov <popov895> |
| Component: | KDE Workspace (Plasma) | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jengelh, nik.kaiser87, pirateclip, popov895, wolfgang |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Picture of blurry fonts | ||
|
Description
Eugene Popov
2022-05-26 09:56:44 UTC
Can confirm. Swapping the font manually to the older hinted ones (for example from https://fonts.google.com/noto/specimen/Noto+Sans) "fixes" the issue, proving that the new otf fonts are not satisfactory. Since literally every existing and new user is affected by this change, which just looks bad, it should be reverted and the old fonts should be used again. Created attachment 859236 [details]
Picture of blurry fonts
Picture of blurry fonts
Hey Pirateclip, this appears to be your change/package ( https://build.opensuse.org/project/show/home:Pi-Cla:branches:M17N:fonts), so I added you to the CC list. Sadly, it had some undesireable effects on the looks of the standard KDE font in Opensuse. Could you maybe revert the changes back to how it was before? For more information, you can have a look at these threads: - https://www.reddit.com/r/openSUSE/comments/ux33f2/bug_todays_update_including_mesadri_snapshot_0522/ia2x2lu/?context=3 - https://www.reddit.com/r/openSUSE/comments/uxphgr/after_the_update_the_notosans_font_became_bolder/ Thank you very much! (In reply to Nik Kai from comment #3) > Hey Pirateclip, this appears to be your change/package ( > https://build.opensuse.org/project/show/home:Pi-Cla:branches:M17N:fonts), so > I added you to the CC list. > > Sadly, it had some undesireable effects on the looks of the standard KDE > font in Opensuse. Could you maybe revert the changes back to how it was > before? > > For more information, you can have a look at these threads: > > - > https://www.reddit.com/r/openSUSE/comments/ux33f2/ > bug_todays_update_including_mesadri_snapshot_0522/ia2x2lu/?context=3 > > - > https://www.reddit.com/r/openSUSE/comments/uxphgr/ > after_the_update_the_notosans_font_became_bolder/ > > Thank you very much! Thanks for CCing me and linking the threads. I was not aware of this previously, I will switch them back to hinted then. Here is the SR: https://build.opensuse.org/request/show/979401 I hope this helps. (In reply to Gordon Leung from comment #5) > Here is the SR: https://build.opensuse.org/request/show/979401 I hope this > helps. Thanks, that was very quick! I will update the Reddit people :) Can someone here try out the unhinted TTF fonts? I have heard that unlike unhinted OTF (which is what the package had switched to). Unhinted TTF gets hinting added to it when used on Linux desktops. If there is no noticeable blurriness then it would be better to switch to unhinted TTF as the file sizes are smaller than hinted TTF. They can be downloaded by cloning this github repo: https://github.com/googlefonts/noto-fonts and then going into unhinted/ttf or by using subversion like so: svn checkout https://github.com/googlefonts/noto-fonts/trunk/unhinted/ttf/ Actually, none of you have to do what I asked above about the unhinted TTFs. The SR has been accepted now, and I am not sure if anyone here (including myself) really cares about smaller file sizes. Either way this should now be resolved. How soon will the fixed font be available in the openSUSE Tumbleweed repos? (In reply to Eugene Popov from comment #10) > How soon will the fixed font be available in the openSUSE Tumbleweed repos? Idk exactly when, but right now it is in the staging process so it should appear very soon. https://build.opensuse.org/request/show/979599 Do you have a screenshot of what you consider the non-blurry state? |