[systemsettings] [Bug 336089] Font preview - rendering problem

[Thomas Sellmaier via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #36 from Thomas Sellmaier  ---
(In reply to Nikos Platis from comment #34)

> While thinking about correcting this bug, one has to remember comment #18:
> if multiple fonts are selected, they appear fine. So this may be easier to
> solve than the convolved code lets one think, and some experienced KDE
> developer could probably decipher this.

Sorry, for my System this workaround still wont work. The only difference is,
that the backround of the preview(s) change to white.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 336089] Font preview - rendering problem

[Thomas Sellmaier via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #35 from Thomas Sellmaier  ---
First of all, I apologize for my harsh sounding post yesterday. My goal was not
to offend someone. But my criticism about favour implementation new features
vs. fixing (old) bugs still remains. 

After a few hours of reading i have to confess that kfontinst IS a hell of
opaque, uncommented code, but the Problem for this issue is IMHO the
/lib/FcEngine class. 

Due to the fact that the whole component is closely interweaved with the system
and that i have no clue about KDE development, it is (by now) not a good idea
to offer my work as a maintainer for this module. But I am on turn to setup a
dev environment, read docs and check whether it is possible for me to maintain
this module in future. If so, i will come forward at the devel mailinglist.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 336089] Font preview - rendering problem

[Thomas Sellmaier via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #30 from Thomas Sellmaier  ---
> Here's a couple of reasons for you:

No, thats no reasons, in this context thats just fine excuses!

>  * the code is at least 6 years old, with the copyrights going back to early
> 2000s
>  * the original author is not around anymore
>  * probably nobody actually wants to dive in *thousands* lines of obscure
> code in their free time
>  * probably nobody understands it

But in context of providing good and reliable software, these excuses ARE
reasons to rewrite this piece of outdated crap. 

Thomas Lübking wrote:
>Craig, the preview seems to use its own rasterizer implementation (and there's 
>xft in the code ;-)

>I wonder whether that's either necessary and feasible (given that Qt5 
>exclusively rasterizes internally now) - or one should just 
>QPainter::drawText() down the lines (also reflecting what it will *really* 
>look like in KDE5 applications)

This makes me think, that it wouldn be *thousands* LOC that nobody
understands This comment is IMHO the result of a short look on the
code.

Dont get me wrong, I really like KDE and enjoy it in my everyeday work and i am
thankful to all of the developers spending their free time. But this issue is
just another example, why open source software often sucks. Instead of taking
bugs serious and fix them, at the latest to the next major release, the
implementation of new features seems to be first in schedule.

> > It makes Plasma look amateurish.
No, It MAKES Plasma/KDE amateurish!

Regards

-- 
You are receiving this mail because:
You are watching all bug changes.