Re: Re: 5.9.1 ...
> > KF5 applications now ignore any other widget style > > except for the space wasting breeze/breeze dark - > > though applications with qt4/kde4 libs dependencies > > like konqueror are not affected. > > > > Used to display window titles with the bold font variants - > > but now those titles are displayed larger but not bold at all. > > (I guess with a different font too) > > > > AND - in kdevelop/kate/kwrite the ability to highlight constants > > or the like with bold fonts has been lost - the color settings are > > still respected, but the bold attribute has no effect anymore ... > > > > ... sadly > > The last update fixed the first and the second issue. > Thanks a lot - this day with breeze style was awful ... > > BUT the latter one - the most important issue for me - still > persists. Despite of chosen settings, the syntax highlighting > in katepart editors does not display keywords or types etc. > in a _bold_ monospaced font, though the font selection dialog > shows a correct preview. Strange enough, if the very same monospace > font in the _bold_ variant has been selected as standard editor > font, the whole code will be displayed bold - as expected ... So, the latter one seems not related to the QT 5.9.1 transition - however - it still persists ... But - in case anyone else encounters that problem, here's a workaround: Each time you change the editor font for kpart editors, in ~/.config/kateschemarc a line will be written like: Font=Hack,10,-1,5,50,0,0,0,0,0,Regular and syntax highlighting in bold or italic won't be displayed anymore. Simply remove the trailing ",Regular" from this line to make it working again.
Re: Note on Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on
Am Samstag, 2. September 2017, 23:46:32 CEST schrieb Luigi Toscano: Morning > Lisandro Damián Nicanor Pérez Meyer wrote: > > I have been told that this creates an interesting impact on Qt's > > performance. Maybe disabling it or removing at-spi2-core where not needed > > might be a good idead until we find a proper solution. > > > > Help with this bug will be highly appreciated, we need to make Debian > > better for everyone. > > The Randa Meetings, a KDE coding sprint which will happen in few days, this > year is focused on accessibility: > https://randa-meetings.ch/2017/06/16/randa-meetings-2017-make-kde-more-acces > sible/ > > Maybe is it worth to relay the issue to them? Even if it is on the Qt level, > a it could get some more attention by expert Qt programmers. I'm reading this list so thanks. Will forward the information. > Ciao Thx Mario
Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1
On Sonntag, 3. September 2017 23:44:30 CEST Miguel A. Vallejo wrote: > > It was also be good to know if the issue goes away if you enable > > antialiasing. > Yes, enabling antialiasing solves the problem. It is just bold text, > rendered fine. But I must turn antialising off. Fuzzy and blurry fonts > produce me headache and visual fatigue. If you have full hinting enabled and well hinted fonts, it shouldn't be blurry,but note modern fonts are typically terribly hinted because they are made more for high res screens or for macs where blurry text is considered part of the key asthethics. For an example of well-hinted fonts I personally recommend the liberation fonts, but only v1, the 2.0 update broke the world class hinting the fonts had, which is why debian has both. Good hinting usually also the only way outline fonts are rendered half decent with antialiasing off. Back to the bug. I made a change in Qt's freetype font engine in 5.9 which is that for OpenType fonts stem darkening was enabled to make antialiasing work better with gamma-corrected blending. Since this is for a special type of antialiasing, it shouldn't happen when antialiasing is disabled, but it is one possibility of something that could have gone wrong and gotten activated when it shouldn't. But another thing that could have gone wrong is that freetype is starting to prioritize non-antialiasing rendering or higher levels of hinting less and less, so newer versions of freetype can often makes such rendering worse. Which is why I asked if you had upgraded that recently. 'Allan
Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1
> Which is why I asked if you had upgraded that recently. Thank for your comments Allan I noticed the problem in the very first boot with Qt 5.9.1, as soon as I opened Dolphin. I don't know if freetype was also upgraded or not at that moment. I remember an upgrade to libfreetype6 some weeks ago that also broke my font rendering. I solved it adding FREETYPE_PROPERTIES="truetype:interpreter-version=35" as commented in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866685 It worked nice and fonts were rendered again as they should be but with Qt 5.9.1 I noticed those particular texts in Qt programs (which seems have bold property enabled) are rendered in a bad form. Everything else in Qt programs is rendered as expected. GTK programs are not affected at all.
