Re: Problem with string to fontset conversion

[Jan D.]

> > > > > Warning: Missing charsets in String to FontSet conversion
> > > > > Warning: Cannot convert string
> > > > > "-*-helvetica-medium-r-*--*-120-*-*-*-*,*" to type FontSet
>
> BTW: the above -*-helvetica-medium-r-*--*-120-*-*-*-* should have two 
> more
> "-*" to be complete.  Maybe that was the problem.

It might have been.  I started with XtDefaultFontSet, which has that 
many dashes, so it is strange.

> > I finally got time to change this.  Now, the old font resource is 
> > used by
> > default.  The fontset handling is only enabled if you specify a 
> > fontset,
> > either on the command line:
>
> Have you had time to investigate to see what's the problem?
> We've been creating fontsets (unless you compile --without-xim) for a 
> long
> time now without any problem, so it's hard to believe that the problem 
> is in
> the Xlib or Xt lib.

I investigated it, but could not reproduce it.  I tried with and 
without the final two "-*".  It just occured to me that I do not run a 
font server.  That might be a difference.


> > % emacs -xrm 'Emacs*fontSet: ...'
> > or in some X resource file (~/.Xdefaults for example).
> > To specify just for popups, do
> > % emacs -xrm 'Emacs*popup*fontSet: ...'
> > and just for the menu bar:
> > % emacs -xrm 'Emacs*menubar*fontSet: ...'
>
> What about those that specify the font via the `menu' face?

That still sets the font resource, not the fontSet resource.  That is 
one more reason to have just one resource.  But if that is not 
possible, it is trivial to change so that if a fontset has been 
specified, the menu face font is stored as an Xt fontSet resource.

        Jan D.