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
Subject: Re: Missing charsets in String to FontSet conversion
Date: Mon, 09 Aug 2010 20:12:00 -0000	[thread overview]
Message-ID: <4C60611D.1010905@dronecode.org.uk> (raw)
In-Reply-To: <4C5833EA.6020002@ece.cmu.edu>

On 03/08/2010 16:21, Ryan Johnson wrote:
> As I mentioned before, I'd seen references to those fonts but wasn't sure it
> would actually help me. I just installed them and, sure enough, there's still
> some (fewer?) missing charsets.
>
> The delay dropped to only 2-3 seconds now though, so I guess that helps. Is
> there a way to diagnose which fonts/charsets are still missing?

Hmm.

You could write a small test application which calls XCreateFontSet() with the 
base font of "*" and reports the list of missing charsets returned.

It also seems that twm reports these problems in a slightly more useful 
fashion than libXt (saying "font for charset <charset> is lacking"), so 
running that (against an X server not started in multiwindow mode) might serve 
just as well.

-- 
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:[~2010-08-09 20:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  8:58 Ryan Johnson
2010-08-03  9:01 ` Thomas Dickey
2010-08-03 13:35   ` Jon TURNEY
2010-08-03 13:46     ` Andy Koppe
2010-08-03 21:31       ` Thomas Dickey
2010-08-03 15:21     ` Ryan Johnson
2010-08-09 20:12       ` Jon TURNEY [this message]
2010-08-09 21:20         ` Ryan Johnson
2010-08-03 15:32     ` Ryan Johnson

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=4C60611D.1010905@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).