![]() Registered Member ![]()
|
At least two ideas were rejected about kword because their resolution should be done (that was the excuse) "upstream"... even if upstream (Qt) does not show the minimum interest on solving them:
1- Better font rendering during editing (I can live without it) 2- Graphite smart font support (my main concern: I only use graphite fonts -and graphite features!- on Writer) I know it is quite soon to ask for any plan, but is it possible to reconsider those ideas (specially the second one! ![]() Thanks, and good luck with this project: the FOSS world really needs a good option to OOo/LibO.
RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2 |
![]() KDE Developer ![]()
|
Your question is pretty well answered here:
http://blog.cberger.net/2010/12/07/call ... omment-712 |
![]() Registered Member ![]()
|
Thanks! That blog provide the answer for half the questions...
![]()
RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2 |
![]() KDE Developer ![]()
|
The answer for the second question is: http://bugreports.qt.nokia.com/browse/QTBUG-13750
or switch to cairo/pango. |
![]() Registered Member ![]()
|
Well, I filled that report. Besides the fact cairo/pango is mainly used by gtk apps, is there any technical reason why this switching is not performed (I mean, other than finding anyone willing to do the job ![]() Don't get me wrong: this questions arise from simple (perhaps naive: I'm not programer) curiosity.
RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2 |
![]() KDE Developer ![]()
|
The dependency itself isn't that much of a problem, I think. Still it's completely different to what we currently use, so it would take months (might even be years) to switch. Currently we expect that the fix in Qt will still be faster. From what we have heard they are working on it, but it's kind of research project and needs work on all plattforms Qt runs on.
It's not like the developer don't acknowledge the problem or are unwilling to fix it, but we simply don't have the capabilities to fix it at the moment. That needs fulltime employed developers who are able to spend enough time on it. |
![]() Registered Member ![]()
|
Perfectly clear. Thanks!
RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2 |
![]() Registered Member ![]()
|
Why do not we make a donation drive and hire someone to fix this problem?
|
Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]