Trolltech has released Qt 3.3.1 with many bugfixes. A Qt Developer Conference for Northeast USA has been announced to be held in Boston on May 10th with Trolltech in attendance. ICS announced a new table widget QicsTable with several advantages over QTable which is dual-licensed under GPL and a commercial license like Qt. The Independent Qt Tutorial has been enlarged and now features a new chapter introducing Qt Widgets for Technical Applications which gives support for advanced plotting and offers a range of new technical widgets.
This version seems to re-introduce an old bug: some fixed width fonts can't be used in konsole (and qtconfig) any more. For example "Courier 10 Pitch" gets apparently replaced by the default system font (Bitstream Vera Sans) in an extreme wide spacing. Very ugly and quite annoying. :-(
Same here ... :-(
This but also was a killer for me ! It's so annoying not to be able to use fixed10 in a terminal ! aaaaargh ... this makes me somewhat happier to know this is an acknowledged bug.
Why do you assume it's an acknowledged bug? It's just reported on a random forum so far, not reported to Trolltech.
06 Mar 2004; Caleb Tennis qt-3.3.1-r1.ebuild,
Add a patch which fixes many font problems for users.
Patch is from Trolltech, and will be in 3.3.2
I have also encountered this bug and another font bug. Some of my
truetype fonts default to some system font. They are not missing in
the list but do not render the way they are supposed to look. I did
file a bug report with the Trolltech people. All these fonts work fine
Yes, that's a regression that appeared in Qt 3.3.1. It has however nothing to do with fixed pitch vs. proportional fonts.
The problem originated from the fact that we started loading bitmapped fonts through Xft2 in Qt 3.3.0. In some cases this lead to Qt loading fonts without Euro character even though there is a font having the Euro available. We tried to fix this in 3.3.1 (as we got some reports about this), but apparently went a bit too far, so FontConfig didn't find a valid font anymore and fell back to the default font (forced to monospace). Why FontConfig is not smart enough to at least substitute a decent monospaced font is another issue....
We have a workaround for this scheduled for Qt 3.3.2 (see attached patch).
If this is not GOOD SUPPORT, support doesn't exists...
Have you ever seen a company that answers a bug report on a forum of a news site with a patch for the bug ?!? Sometimes, I really take out the hat for TrollTech.
I can't agree more. You guys at Trolltech have made programming fun again. It's just that simple. Trolltech really feels like a company that cares about it's customers and people in general, not to mention making a quality product. Bravo!
I was hoping Lindows would include Qt 3.3.1. I guess it will probably have 3.3.2 if it is released really fast or 3.2.x.
Or they will release Qt 3.3.1 with the patch. Its common for distros to package with such patches... on Gentoo for XFree86 there are dozens of patches it applies. There are usually a few for Qt.
I have rebuilt the qt-3.3.1 rpm with the above patch and
recovered all my fonts....problem solved....thanks.
I used qt-copy from the KDE CVS repository. And yes, it includes the patch, and a whole others. Thanks for providing it too.
In file included from kernel/qfontdatabase.cpp:633:
kernel/qfontdatabase_x11.cpp: In function `QFontEngine*
loadFontConfigFont(const QFontPrivate*, const QFontDef&, QFont::Script)':
kernel/qfontdatabase_x11.cpp:1798: `family' undeclared (first use this
OK, ignore me. I had misapplied the patch.
Move on, nothing to see here...
Sorry for OT, but this is related to fonts, and I don't have platforms different enough to test to see what is the source of the problem: KDE, Qt, ot Redhat.
I am using KDE 3.1.4 on Red Hat 9, i used to use 3.0.x (default installation) on RH8... and I installed TT fonts from my XP.
Strange problem is that when I choose fonts, font preview is not same as what I see in app. I have to choose 2pts larger fonts. I mean, preview is 2pts larger than what realy appears in apps. What could be the source of this strange problem?
PS Qt and KDE teams, I admire for your good^H^H^H^H excellent work!
Any one know if the KGet problem (http://bugs.kde.org/show_bug.cgi?id=75429) introduced with QT3.3 is fixed in 3.3.1?