public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Andy <AndyMHancock@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: xfig: Warning: Missing charsets in String to FontSet conversion
Date: Mon, 04 Feb 2013 00:14:00 -0000	[thread overview]
Message-ID: <loom.20130204T011044-564@post.gmane.org> (raw)

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.  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:

   [  6157.577] XFree86-Bigfont extension local-client optimization
   disabled due to lack of shared memory support in the kernel

   [  6157.640] [dix] Could not init font path element
   /usr/share/fonts/OTF/, removing from list!

I don't care about "optimizations" at this point, so I ignored the first
message.  Googling "OTF" in the 2nd message reveals that they are
Adobe/Microsoft fonts, so I doubt that is the problem.  In any case, I would
like to avoid installing fonts willy-nilly because there are so many and I don't
want to bloat my system.

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


--
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  0:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  0:14 Andy [this message]
2013-02-04 15:26 ` Jon TURNEY
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=loom.20130204T011044-564@post.gmane.org \
    --to=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).