public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: AndyMHancock@gmail.com
Subject: Re: xfig: Warning: Missing charsets in String to FontSet conversion
Date: Mon, 04 Feb 2013 15:26:00 -0000	[thread overview]
Message-ID: <510FD313.2000608@dronecode.org.uk> (raw)
In-Reply-To: <loom.20130204T011044-564@post.gmane.org>

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
> 
> I want to deal wit the font messages first.  I may ask about the compose key
> file if I can't resolve it with web search.
> 
> Googling the font error yields hits mostly from non-cygwin distributions of
> xfig.  Most hits are from people who actually get more detail in the error,
> specifying the fonts that are missing.

Interesting.  Maybe there is some patch available which improve the reporting
in libX11.

> I don't seem to have that detail in the
> message above.  I found that the fonts are stored in /usr/share/fonts, but I
> haven't been able to find a description of how to determine which fonts are
> missing.  The only font related messages in the XWin log file at
> /var/log/xwin/XWin.0.log are:
> 

> 
> Is there an xfig log file or some other means by which one can determine which
> fonts are missing?

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.

-- 
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/


  reply	other threads:[~2013-02-04 15:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  0:14 Andy
2013-02-04 15:26 ` Jon TURNEY [this message]
2013-02-05  0:27   ` Jack
2013-02-05  7:05     ` Andy
2013-02-12 14:12       ` Jon TURNEY
2013-02-12 14:42         ` marco atzeri
2013-02-12 15:42           ` Jon TURNEY
2013-02-12 15:53             ` marco atzeri
2013-02-13 17:17         ` Jack
2013-02-13 21:47           ` Thomas Dickey
2013-02-13 22:48             ` Jack
2013-02-13 23:26               ` Thomas Dickey
2013-02-14 16:15           ` Jon TURNEY
2016-05-22 13:27 Stefan Katletz
2016-05-22 13:55 ` Stefan Katletz
2016-05-22 14:21   ` Marco Atzeri
2016-05-22 20:47 ` Stefan Katletz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=510FD313.2000608@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=AndyMHancock@gmail.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).