That is truly odd. How come the XIM code doesn't trigger this same problem?
I think the XIM code explicitly names the charset it wants.
But our XIM code calls XCreateFontSet, just like Xt code.
And browsing the Xt source, the "Cannot convert string to FontSet" message
seems to be generated when XCreateFontSet returns NULL, so maybe
we could track it down further by making an appropriate call to XFontSet and
seeing what it returns. Presumably it will return NULL but with a non-zero
list of missing charsets.
I've attached a test program.
Jan D.
#include <stdio.h> #include <X11/Xlib.h>
int
main(int argc, char *argv[])
{
Display *dpy = XOpenDisplay(NULL);
char *fn = argc > 1 ? argv[0]
: "-*-helvetica-medium-r-*--*-120-*-*-*-*-*-*,*";
char **missing;
int cnt, i;
if (!dpy)
{
fprintf(stderr,"Can't open display %s\n", XDisplayName(NULL));
return -1;
}
XCreateFontSet(dpy, fn, &missing, &cnt, NULL);
for (i = 0; i < cnt; ++i)
printf("Missing %d: %s\n", i, missing[i]);
return 0;
}
_______________________________________________ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
