Fwd: Build results for xemacs-sjt-xft
Repost due to filter lossage. Gmail doesn't have a bounce so I'm
forwarding, sorry.
---------- Forwarded message ----------
From: James Crippen <jcrippen(a)gmail.com>
Date: Tue, 28 Dec 2004 21:08:02 -0900
Subject: Build results for xemacs-sjt-xft
To: XEmacs-beta <xemacs-beta(a)xemacs.org>
Just pulled the current CVS of xemacs-sjt-xft branch and built. Seemed
to build without much problem, although I did have to add
--cppflags="-I/usr/include/freetype2" to configure because it still
doesn't seem to find the include directory for freetype. This would be
fixed if pkg-config is used in the configure script, saying something
like "pkg-config --cflags freetype2". This should work on all
installations which have Xft, AFAIK, because Xft has its own
pkg-config info as well.
Build seems to work okay. Fires up and displays text in Courier at a
reasonable size, which is nice. But *everything* causes the following
warnings in *Warnings*:
(90) (xft/warning) ("missing font in update_widget_face" . buffers-tab)
(133) (xft/warning) ("missing font in update_widget_face" . widget)
this is probably because I have no X resource set for them? I'll set
some and see if this fixes the warnings later.
I can't send a build report. I say "M-x build-report", get a buffer
face warning, type "Success" and press enter, and nothing happens,
point is back in *scratch* buffer, and I get "Wrong number of
arguments: find-file, 3" in the echo area. This sounds like a package
issue, since I haven't installed it yet (I'm just running src/xemacs
by hand).
Also, I'm not sure what to do to get CJK to display correctly (this is
a Mule build). I got this warning:
(65) (xft/warning) ("unknown charset" #<charset chinese-gb2312
"GB2312" "GB2312)" "GB2312 Chinese simplified" 94x94 l2r
cols=2 g0
final='A' reg=gb2312 0x1bf>)
(66) (xft/warning) ("unknown charset" #<charset chinese-gb2312
"GB2312" "GB2312)" "GB2312 Chinese simplified" 94x94 l2r
cols=2 g0
final='A' reg=gb2312 0x1bf>)
when trying to open a file containing UTF-8 text with Japanese in it.
And I only see a few kanji characters displayed in what looks
suspiciously like a Chinese font. Is this because fontconfig is
selecting some random font to display the characters and it's losing
with the wrong default font?
If I wanted to edit only Latin text it looks like it would work fine.
The enriched doc sample looks okay, although it's somewhat ugly. I
can't display the hello sample because I get the "find-file, 3" error
again.
Let me know what to do to work around the find-file error and I'll get
some X resources configured and get a build-report sent. Then I can
record some of the copious error/warning messages from the terminal
and figure out what's going wrong with font selection.
I really want to see Xft make it into 22.0, and I'm willing to do
anything I can to beta test it.
James