I think the rendering model of LyX is different. It doesn't do WYSIWYG.

So for now we don't have a clue how to fix the problem. The only thing we can do is to vote on the Qt bugtracker and hope that Nokia manages to fix the problem at some point.

Vote here:
http://bugreports.qt.nokia.com/browse/QTBUG-10615
http://bugreports.qt.nokia.com/browse/QTBUG-205

=> http://bugreports.qt.nokia.com/browse/Q ... ion_116167
=> https://bugs.kde.org/show_bug.cgi?id=237305#c4

on 2010-05-12:

"Qt's text rendering is mainly for UI purposes and we cannot attempt to compete with typographical grade text applications, so I'm closing this task as out of scope."

I'm wondering how much an office suite can do with a backend for text rendering that doesn't consider itself typographical grade.
I think Koffice developers should look into using something other than Qt itself to render the text, since, according to Qt developers, the toolkit is obviously not meant for any kind of complex text rendering.

I am afraid that just hoping Koffice font problem will be solved one day by qt team is not enough to expect a solution.

The reply by Sven is still a good one; if you are bothered by this issue vote for it and get the people that can fix it a bit of feedback on how many people it affects. I've mentioned this before in this thread and we had 2 votes yesterday, so obviously its not that big a deal to that many people.

And I can see why its not that big a deal as its very easy to work around. You can set a normal font hinting. See Svens blog again; http://slangkamp.wordpress.com/2009/09/ ... rendering/

Next to that, on normal screens (i.e. DPI of 90 or higher) the issue just doesn't occur on normal font sizes. Where normal is 10pt or taller. The default font size when starting KWord is 12pt and even zooming in very far has no negative effects on font quality.

So, yes, sure, the bug should be fixed, Nokia developers putting time into that would be wonderful. So please vote.
At the same time you can do a lot to avoid this problem hitting you. And if you use a common distro like (k)ubuntu the default settings are just fine and you won't have this issue.
For reference; this is what it looks like on a default setup on a macbook. http://yfrog.com/0ifontsop

zander wrote:And I can see why its not that big a deal as its very easy to work around. You can set a normal font hinting.

No, no and no. Explanation already made many times. Not necessary to repeat again (read bug reports).
Once your system font is fine and finetuned, you don't touch it anymore. => http://imagik.fr/view-rl/134151

So, yes, sure, the bug should be fixed, Nokia developers putting time into that would be wonderful. So please vote.

Nokia developers ? You mean qt developers ? Answer is clearly no, they will not work on a bug they are not concerned with, as they explain.

Please vote ? How do you expect people not using Koffice, because unusable, voting for a bug ? They just use OOo, that's it.
A developer should not wait counting votes for a bug which "should be fixed".

You say: "the bug should be fixed": definitely yes, it should have been long time ago, or no, if Koffice is not used and not identified necessary anymore by KDE team (my feeling).

Well, I've made my conclusion on that one.

________________
special note for KDE Karma's hidden moderator: so sorry if a developer reading this has been hurt by user comment.

@L_V:

Your above quote from http://bugreports.qt.nokia.com/browse/Q ... ion_116167 does not reflect the original.
Only the first sentence is a real quote. Can you please update your post accordingly to refeclt a real quote?
Thanks

neverendingo wrote:Only the first sentence is a real quote. Can you please update your post accordingly to reflect a real quote?Thanks

I've used the KDE copy/paste feature; so might be a "real quote".
I've just added the exact/real link.

@L_V the "I'm wondering how"... sentence should not be in the quote braces then, as thats not part of the quote.

zander wrote:@L_V the "I'm wondering how"... sentence should not be in the quote braces then, as thats not part of the quote.

It's good to see you have so much time to compare so many font bug reports, or even try to find typos.

"I'm wondering how" comes from this one: https://bugs.kde.org/show_bug.cgi?id=237305#c4

Hope this is not the more complex problem you have to solve, considering that this font bug exists since the very beginning of Kword 1, many many years ago.

If you look at the bug report you can see that the bug wasn't closed and that the end of the the discussion is different (see the last four comments).

So the bugs are still open, but not very high priority. That's why you should vote. Even if only the people in this thread vote.

What is the status of this font rendering bug in Koffice since Qt team says:

"Qt's text rendering is mainly for UI purposes and we cannot attempt to compete with typographical grade text applications"

Is KDE team still expecting something from Qt that they will never have ?
Or simply, Koffice will remain unusable ?

Or do I miss something since this bug is claimed "resolved" ?
Bug 237305 - better koffice font rendering

Work has started to fix this. See http://bugreports.qt.nokia.com/browse/QTBUG-10615
It will take some time though.

@L_V notice that the report you see as 'resolved' is resolved as upstream what this means in practical terms is that its not a KOffice task. Its a task to be done inside of Qt. The fact is that Qt is the upstream of KOffice, which makes those pieces of the confusing puzzel fit better together

The bug for Qt is open so your quote seems to be outdated. The bug is linked to by sven above and also its linked to in the kde bugzilla bugreport, so this should be the authoritive bugreport.

Bottom line is that you don't have to worry; there is a simple and acceptable workaround right now and there is a proper solution on the way.

Thanks for your concern, I hope we'll get the required feature in Qt soon

zander wrote:I hope we'll get the required feature in Qt soon

"Hope", "Soon" ... are you really a developer to speak like this ?
"Soon" was what was said few years ago.

I'm afraid that just hoping and waiting, or just pointing "the fault to Qt" will not help.
Koffice is not seriously managed.

The developers from Nokia are working on the problem. It's quite a difficult task as it needs work on every plattform Qt is running on. It would take quite a long time for KOffice developers to dive into that area of Qt.

Seriously, what are you expecting us to do? It's not like we have an army of full-time developers hidden somewhere.

Years have been lost by claiming that there is no font rendering problem, and that "you can slightly improve it by modifying the aliasing of your complete system", assuming Koffice is the central piece of your system (...)
This problem is known since the very beginning of Koffice .. years ago.
It should have been much more obvious even to a basic developer that this font rendering problem was a blocking one, and then should have been managed more professionally with the help of Qt.

When Qt says this: "Qt's text rendering is mainly for UI purposes and we cannot attempt to compete with typographical grade text applications".

it simply means that Koffice team has made a wrong technical choice.

Koffice development has been very slow for years, because "hoping" and expecting/waiting things for "soon" is far to be the right attitude to seriously track key issues.