> That's disturbing. Perhaps Qt is doing something weird.
You bet. Other bits of weirdness:
- I specify the non-Cyrillic font "Bistream Vera Sans" (bold, 11
point) for window titles, and KDE supplies Cyrillic characters
from a serif instead of a sans-serif font (see attached
screenshot).
- I specify "Bistream Vera Serif" (12 point) as my default font
in Konqueror, and for non-bold text KDE supplies ugly
spaced-out Cyrillic glyphs from one of the Chinese fonts,
whereas glyphs for bold Cyrillic text are apparently fetched
from the same source as in Window titles (screenshot in
separate email due to the list's message size restriction).
> One way to test would be to install fontconfig 2.2.93 and use
> the (new) 'fc-match' application to see how the configuration is
> affecting the list of fonts provided back to the application.
The most recent development snapshot (2.2.92) fails to build with
the attached error message. The CVS version fails to configure
with the other attached error message.
Stefan
--
Stefan Baums
Asian Languages and Literature
University of Washington
-------------- next part --------------
A non-text attachment was scrubbed...
Name: window-title.png
Type: image/png
Size: 14144 bytes
Desc: not available
Url : http://freedesktop.org/pipermail/fontconfig/attachments/20040422/612501e7/window-title-0001.png
-------------- next part --------------
/tmp/fontconfig-2.2.92> make
make all-recursive
make[1]: Entering directory `/home/tmp/fontconfig-2.2.92'
Making all in fontconfig
make[2]: Entering directory `/home/tmp/fontconfig-2.2.92/fontconfig'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/tmp/fontconfig-2.2.92/fontconfig'
Making all in fc-lang
make[2]: Entering directory `/home/tmp/fontconfig-2.2.92/fc-lang'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -I.. -I/usr/include/freetype2 -g -O2 -MT fc-lang.o -MD -MP -MF ".deps/fc-lang.Tpo" \
-c -o fc-lang.o `test -f 'fc-lang.c' || echo './'`fc-lang.c; \
then mv -f ".deps/fc-lang.Tpo" ".deps/fc-lang.Po"; \
else rm -f ".deps/fc-lang.Tpo"; exit 1; \
fi
In file included from ../fontconfig/fcfreetype.h:27,
from ../src/fcint.h:39,
from fc-lang.c:25:
/usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!"
/usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files."
/usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:"
/usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>"
/usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H"
make[2]: *** [fc-lang.o] Error 1
make[2]: Leaving directory `/home/tmp/fontconfig-2.2.92/fc-lang'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tmp/fontconfig-2.2.92'
make: *** [all] Error 2
-------------- next part --------------
/tmp/fontconfig> autoconf
configure.in:36: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:37: error: possibly undefined macro: AM_MAINTAINER_MODE
configure.in:55: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:60: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
configure.in:61: error: possibly undefined macro: AM_PROG_LIBTOOL
configure.in:73: error: possibly undefined macro: AM_CONDITIONAL
/tmp/fontconfig> ./configure
./configure: line 1306: syntax error near unexpected token `fontconfig,'
./configure: line 1306: `AM_INIT_AUTOMAKE(fontconfig, 2.2.93)'
