qpe on qvfb finds no font, because "qbuild image" does not install any ttf

[ydirson]

Only empty squares are displayed in place of text characters, starting from firstuse screen.

If I add the patch below, the only trace I have says : paintEvent font: "" -1 The fontdatabase really seems empty...

--- a/src/server/ui/components/firstuse/firstuse.cpp +++ b/src/server/ui/components/firstuse/firstuse.cpp @@ -24,6 +24,7 @@

include "../../../../settings/language/languagesettings.h"

include

+#include

include

include

@@ -38,6 +39,7 @@

include

include

include

+#include

include "qtopiainputevents.h"

@@ -508,6 +510,12 @@ void FirstUse::paintEvent(QPaintEvent *) f.setPointSize(8); f.setItalic(false); f.setBold(false);

• QFontInfo fi(f);
• qLog(UI) << "paintEvent font: " << fi.family() << " " << fi.pixelSize(); +
• QFontDatabase database;
• foreach (QString family, database.families())

• qLog(UI) << " available font fam: " << family;

  p.setFont(f); p.setPen(QPen(Qt::black));

[ydirson]

Using -runmode stace I discover about /tmp/qtembedded-0/fonts/fontdb, which is pretty much empty on the host, while it is much larger on the device, where it contains paths to .ttf files, while image/lib/fonts/ only contains .qpf2 files.

A simple "cp ../qtmoko/qtopiacore/qt/lib/fonts/*ttf image/lib/fonts/" is sufficient to get things working, the qbuild image target seems to need some fixing.

[ydirson]

In fact, the relevant fonts are not even installed when building for the device, where /opt/qtmoko/lib/fonts is instead a symlink to /usr/share/fonts/truetype/ttf-dejavu, where the fonts are installed by another package.

This seems to advocate for:

• moving the creation of this symlink from the debian packaging to qbuild files
• adding explicit dependency on the dejavu fonts on host
• removing ttf files from source tree (hm, that's the qt official tree, so maybe not...)

[ydirson]

OK, what happens is somewhat more clear:

• the build system only has support for choosing among the fonts shipped in the tree, not any from the system
• the devices/*/configure-common files request installation of qpf2 files only, although the required DejaVu fonts are available as already noted
• qtmoko does not enable the use of QPF2 files (qconfig-qpe.h has QT_NO_QWS_QPF2 since 3a22a95573, that was before v10)

Things to be done:

• the -add-font mechanism does not have a wildcard mechanism for ttf fonts, so currently it would require listing all DejaVu fonts, which would be bad (have a patch for interpreting -add-font as a regexp, that would help). That would aleady result in a working image/ tree.
• make a decision about qpf2. Either we drop their support completely and nuke them from all devices' configure-common, or we re-enable them. Isn't therea single advantage about them ? I'm mostly thinking about display speed, which is something we must improve...

Additional things do maybe do:

• those -add-font flags and a log of things are pretty generic, they should live in an über-common file
• support for using system fonts instead of restricting the list and copying files would be better
• if wee keep support for qpf2 fonts, have them generated using makeqpf instead of blindly using the ones prebuilt by Nokia years ago using an old version of the fonts (could that be the source of existing problems ?)