[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2018-07-06 Thread Woko
I just installed the new KDE Neon Bionic version as a VM. The Trick doesn't work there. The freetype-version is 2.8.1-2ubuntu2 like on the Kubuntu Host. Maybe the /etc/environment is ignored there. I'm just researching. -- You received this bug notification because you are a member of Kubuntu

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2018-03-03 Thread roots
Thanks Martin, this did the trick with Ubuntu 18.04 as well. Cheers, r. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1722508 Title: Font hinting appears broken on 17.10 beta To manage

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2018-01-30 Thread Woko
I can report that the solution Martin reported works also for Monospace in Konsole-sessions. Because it's much better than downgrading, I removed all the changes I described in #23 and it works like a charm. Thanks a lot Martin! Wolfram -- You received this bug notification because you are a

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2018-01-05 Thread gldickens3
Hi Martin, Thanks for the tip! Defining the FREETYPE_PROPERTIES as you suggested in /etc/environment did indeed disable hinting and renders the same crisper fonts as was in earlier versions of Ubuntu. Personally, I still prefer to disable hinting in the source code but your suggestion works

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-12-24 Thread Martin Dauskardt
In german ubuntuusers forum there is an simpler solution without need to downgrade libfreetype. https://forum.ubuntuusers.de/post/8914328/ Just add FREETYPE_PROPERTIES="truetype:interpreter-version=35 cff:no-stem- darkening=1 autofitter:warping=1" in /etc/environment and restart x-server or

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-12-01 Thread Jeremy Bicha
> Its not so much that the font rendering is better or worse but that it is different than before Gordon, thanks for your reply. I think your issue is different than the Qt issue mentioned by many of the commenters here. I help maintain Ubuntu's font packages, but I just started with that and I

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-12-01 Thread gldickens3
Hello jbicha, I am not running Kubuntu but I am running KDE Plasma 5 and Qt apps on several OpenSUSE installations. On my Ubuntu installation I am running Gnome Shell. As an FYI, I maintain a freetype2 repository with subpixel rendering enabled for OpenSUSE Leap and Tumbleweed. Like most of the

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-30 Thread Ubuntu Foundations Team Bug Bot
The attachment "Patch to disable #define TT_CONFIG_OPTION_SUBPIXEL_HINTING" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-30 Thread Jeremy Bicha
Gordon, according to earlier comments, the Qt part of this bug will be fixed before 18.04 LTS's release. Are you using Kubuntu or Qt apps? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report.

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-30 Thread gldickens3
In the first line of third paragraph of my prior post I meant to say "(commented out)" instead of "(uncommented)" So, that line should read: "This needs to be undefined (commented out) in order for freetype-2.7 and 2.8 to render fonts identically to prior versions of Ubuntu freetype

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-30 Thread gldickens3
One of the primary differences in freetype-2.8 and prior Ubuntu versions of freetype is the introduction of TT_CONFIG_OPTION_SUBPIXEL_HINTING in /include/freetype/config/ftoption.h in freetype-2.7.X and later. The default value is: #define TT_CONFIG_OPTION_SUBPIXEL_HINTING 2 This needs to be

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-28 Thread imachine
Then see here the correctly displayed fonts on Gmail (also downloaded from Gmail's server, no local font). Works fine and hints correctly. What gives? Running last stable firefox (56.0, 57 all messed up, so locked 56 with apt-lock) Ubuntu 17.10 ** Attachment added: "Screenshot-2017-11-28

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-10 Thread Ragnar Dunbar
In 17.10 (Gnome), when I change the font to 'Ubuntu Mono Regular', as I always do, and switch to Antialiasing LCD in gnome-tweak-tool and Hinting to Full, fonts look messy. When I do the same in Ubuntu 16.04 via unity-tweak-tool, fonts are crisp and sharp. Comparison is depicted in the attachment.

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-10 Thread Jeremy Bicha
** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Also affects: qt Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed ** Changed in: qtbase-opensource-src (Ubuntu) Importance:

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-10 Thread Woko
I had the same Problem. The monospace-font in konsole looked ugly after upgrade from 17.04. Same with freetype 2.8.1. Then I downgraded libfreetype to 2.6.3 as HorstBort mentioned, and konsole looks nice again. Here the description how I managed it: 1. add 'deb http://archive.ubuntu.com/ubuntu/

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-06 Thread mrvanes
In my (humble) opinion the best way to solve this thinking forward, is to upgrade to freetype 2.8.1, plasma 5.11 and adjust font queries in kdeglobals and trolltecht.conf without weight specific strings as described in this bug: https://bugreports.qt.io/browse/QTBUG-63792 It's also nice to see

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-29 Thread mrvanes
Then, my advise would be to backport the TT hinting fix to 2.8.0 in Artful for all those not able to use 2.8.1 from ppa? Bionic is still a long way to go. Anyway, all is fine for me, so feel free to decide as you see fit... -- You received this bug notification because you are a member of

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-28 Thread Jeremy Bicha
We can't update freetype to 2.8.1 in Ubuntu 17.10 because it will break Electron apps (LP: #1728329). But Ubuntu 18.04 LTS will likely get freetype 2.8.1 (or possibly a newer version). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-26 Thread mrvanes
No, only half of the problem was caused by libfreetype 2.8.0 (normal TT hinting) but should indeed be updated as soon as possible in Artful, the other part (bold/italics) is a Qt 5.9.x problem and needs some love from Qt. -- You received this bug notification because you are a member of Kubuntu

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-26 Thread Denis Kalinin
Yeah, I'm not sure what progress could be made at this point. The way I see it, the issue was resolved in a new version of libfreetype (2.8.1). The only thing that is left is to propagate the fix to main Ubuntu repo. -- You received this bug notification because you are a member of Kubuntu

[Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-26 Thread mrvanes
In the meantime the problem has been narrowed down to QFont::toString() appending too much fontstyle information. https://bugs.kde.org/show_bug.cgi?id=376630 https://bugs.kde.org/show_bug.cgi?id=378523 With Qt being alerted and kde having more issues reported I think problem reveived more than