Re: xfig: Warning: Missing charsets in String to FontSet conversion

[Jon TURNEY <jon.turney@dronecode.org.uk>]

On 05/02/2013 07:05, Andy wrote:
> Jack <ostroffjh <at> sbcglobal.net> writes:
>> On 2013.02.04 10:26, Jon TURNEY wrote:
>>> On 04/02/2013 00:11, Andy wrote:
>>>> When I start xfig, I get the following:
>>>>    Warning: Missing charsets in String to FontSet conversion
>>>>    Warning: Missing charsets in String to FontSet conversion
>>>>    Warning: Missing charsets in String to FontSet conversion
>>>>    ^GCan't open compose key file '/usr/lib/xfig/CompKeyDB',
>>>>       no multi-key sequences available
>>>
>>> Yes, this error message from libX11 is pretty bad, and should tell
>>> you the charsets that are missing.
>>>
>>> If I recall correctly, this warning is usually caused when you are
>>> using an UTF-8 locale (like the default C.UTF-8 locale), because
>>> when making the fontset, libX11 searches for matching fonts with
>>> all the encodings it knows about, and there are no matching fonts
>>> with CJK encodings (as no CJK fonts are installed).
>>>
>>> Installing the fonts font-isas-misc, font-jis-misc and
>>> font-daewoo-misc should work around the problem.
>>>
>>> You could also use a non-UTF-8 locale, but I wouldn't recommend
>>> that.

>> I'm getting the same three warnings, followed by
>> Warning: Cannot convert string
>> "-*-times-bold-r-normal--16-*-*-*-*-*-*-*,-*-*-bold-r
>> -normal--16-*-*-*-*-*-*-*,-*-*-*-r-*--16-*-*-*-*-*-*-*"
>> to type FontSet

>> I already have those three fonts installed, and my locale is
>> en_US.UTF-8.
> 
> Ah well.  Seems like it was a good attempt at guessing the cause, but those
> fonts weren't the problem.
> 
>> I see some similar issues in the past in the list archive, including
>> an unanswered post from Yaakov 17 Dec 2009 which looks exactly like
>> this question.
>>
>> I've also seen posts suggsting other fonts or packages - none of
>> which I see on cygwin, so I don't know if they're not available or
>> just named differently.  (Examples include gsfonts-x11, xfonts-base,
>> xfonts-encodings, xfonts-scalable)
> 
> Yes, I saw some of these as well, notably gsfonts-x11.  I didn't jump to the
> conclusion that those particular fonts were my problem because they seem to vary
> from situation to situation.  And, as you noted, gsfonts-x11 is not part of a
> cygwin package (at least from a package search).
> 
>> Any other troubleshooting you can suggest?

I've uploaded at [1] a patched version of libXt, which includes some extra
debugging output, including the name of encoding which is causing this
warning, based on a patch at [2].  (This patch isn't really suitable for
upstreaming as it needs to be wired up to libXt's rather confusing error
reporting and localization scheme)

This should at least allow us to discover the name of the encoding which is
causing the warning.

[1] ftp://cygwin.com/pub/cygwinx/cygXt-6.dll
[2] http://lists.gnu.org/archive/html/help-gv/2010-07/msg00004.html

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/