public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
* Missing charsets in String to FontSet conversion
@ 2010-08-03 8:58 Ryan Johnson
2010-08-03 9:01 ` Thomas Dickey
0 siblings, 1 reply; 9+ messages in thread
From: Ryan Johnson @ 2010-08-03 8:58 UTC (permalink / raw)
To: cygwin-xfree
Hi all,
At some point an annoyance appeared with my xterm windows: The first
time I use [ctrl]+mouse click in any window, that xterm becomes
unresponsive for about 5 seconds with the CPU pegged to 100%. After the
five seconds is up, whatever shell spawned the xterm receives the
following message:
> Warning: Missing charsets in String to FontSet conversion
After that all works normally (until I open the next xterm window).
Is there a way to diagnose what the problem is? I don't know what
FontSet string the error even refers to, let alone which parts of that
string were invalid. In any case, it really shouldn't take five seconds
of hard CPU crunching to detect and report an invalid input string.
I found one message from last year's archives that mentioned certain
Japanese fonts, but in that case they knew which fonts were missing. I'd
rather not go installing every font known to man just in hopes of
catching the missing one.
Thoughts?
Ryan
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Missing charsets in String to FontSet conversion
2010-08-03 8:58 Missing charsets in String to FontSet conversion Ryan Johnson
@ 2010-08-03 9:01 ` Thomas Dickey
2010-08-03 13:35 ` Jon TURNEY
0 siblings, 1 reply; 9+ messages in thread
From: Thomas Dickey @ 2010-08-03 9:01 UTC (permalink / raw)
To: cygwin-xfree
On Tue, 3 Aug 2010, Ryan Johnson wrote:
> Hi all,
>
> At some point an annoyance appeared with my xterm windows: The first time I
> use [ctrl]+mouse click in any window, that xterm becomes unresponsive for
> about 5 seconds with the CPU pegged to 100%. After the five seconds is up,
> whatever shell spawned the xterm receives the following message:
>> Warning: Missing charsets in String to FontSet conversion
>
> After that all works normally (until I open the next xterm window).
>
> Is there a way to diagnose what the problem is? I don't know what FontSet
> string the error even refers to, let alone which parts of that string were
> invalid. In any case, it really shouldn't take five seconds of hard CPU
> crunching to detect and report an invalid input string.
This topic came up last year, iirc the issue was this:
http://invisible-island.net/xterm/xterm.faq.html#slow_menus
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Missing charsets in String to FontSet conversion
2010-08-03 9:01 ` Thomas Dickey
@ 2010-08-03 13:35 ` Jon TURNEY
2010-08-03 13:46 ` Andy Koppe
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Jon TURNEY @ 2010-08-03 13:35 UTC (permalink / raw)
To: cygwin-xfree; +Cc: ryanjohn
On 03/08/2010 10:00, Thomas Dickey wrote:
> On Tue, 3 Aug 2010, Ryan Johnson wrote:
>> At some point an annoyance appeared with my xterm windows: The first time I
>> use [ctrl]+mouse click in any window, that xterm becomes unresponsive for
>> about 5 seconds with the CPU pegged to 100%. After the five seconds is up,
>> whatever shell spawned the xterm receives the following message:
>>> Warning: Missing charsets in String to FontSet conversion
>>
>> After that all works normally (until I open the next xterm window).
>>
>> Is there a way to diagnose what the problem is? I don't know what FontSet
>> string the error even refers to, let alone which parts of that string were
>> invalid. In any case, it really shouldn't take five seconds of hard CPU
>> crunching to detect and report an invalid input string.
There's some more discussion at
http://sourceware.org/bugzilla/show_bug.cgi?id=10948
Installing the fonts font-isas-misc, font-jis-misc and font-daewoo-misc should
also work around the problem, which can also be seen with other applications,
as that ensures that at least one font exists for every charset.
I agree that the error message sucks and should tell you the charsets which
are missing and what string it was attempting to convert.
> This topic came up last year, iirc the issue was this:
>
> http://invisible-island.net/xterm/xterm.faq.html#slow_menus
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Missing charsets in String to FontSet conversion
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-03 15:32 ` Ryan Johnson
2 siblings, 1 reply; 9+ messages in thread
From: Andy Koppe @ 2010-08-03 13:46 UTC (permalink / raw)
To: cygwin-xfree
On 3 August 2010 14:35, Jon TURNEY wrote:
> On 03/08/2010 10:00, Thomas Dickey wrote:
>>
>> On Tue, 3 Aug 2010, Ryan Johnson wrote:
>>>
>>> At some point an annoyance appeared with my xterm windows: The first time
>>> I
>>> use [ctrl]+mouse click in any window, that xterm becomes unresponsive for
>>> about 5 seconds with the CPU pegged to 100%. After the five seconds is
>>> up,
>>> whatever shell spawned the xterm receives the following message:
>>>>
>>>> Warning: Missing charsets in String to FontSet conversion
>>>
>>> After that all works normally (until I open the next xterm window).
>>>
>>> Is there a way to diagnose what the problem is? I don't know what FontSet
>>> string the error even refers to, let alone which parts of that string
>>> were
>>> invalid. In any case, it really shouldn't take five seconds of hard CPU
>>> crunching to detect and report an invalid input string.
>
> There's some more discussion at
> http://sourceware.org/bugzilla/show_bug.cgi?id=10948
>
> Installing the fonts font-isas-misc, font-jis-misc and font-daewoo-misc
> should also work around the problem, which can also be seen with other
> applications, as that ensures that at least one font exists for every
> charset.
>
> I agree that the error message sucks and should tell you the charsets which
> are missing and what string it was attempting to convert.
>
>> This topic came up last year, iirc the issue was this:
>>
>> http://invisible-island.net/xterm/xterm.faq.html#slow_menus
Could the menuLocale resource setting mentioned there be added to
Cygwin xterm's default config at /etc/X11/app-defaults/XTerm?
Andy
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Missing charsets in String to FontSet conversion
2010-08-03 13:35 ` Jon TURNEY
2010-08-03 13:46 ` Andy Koppe
@ 2010-08-03 15:21 ` Ryan Johnson
2010-08-09 20:12 ` Jon TURNEY
2010-08-03 15:32 ` Ryan Johnson
2 siblings, 1 reply; 9+ messages in thread
From: Ryan Johnson @ 2010-08-03 15:21 UTC (permalink / raw)
To: cygwin-xfree; +Cc: Jon TURNEY
On 8/3/2010 3:35 PM, Jon TURNEY wrote:
> On 03/08/2010 10:00, Thomas Dickey wrote:
>> On Tue, 3 Aug 2010, Ryan Johnson wrote:
>>> At some point an annoyance appeared with my xterm windows: The first
>>> time I
>>> use [ctrl]+mouse click in any window, that xterm becomes
>>> unresponsive for
>>> about 5 seconds with the CPU pegged to 100%. After the five seconds
>>> is up,
>>> whatever shell spawned the xterm receives the following message:
>>>> Warning: Missing charsets in String to FontSet conversion
>>>
>>> After that all works normally (until I open the next xterm window).
>>>
>>> Is there a way to diagnose what the problem is? I don't know what
>>> FontSet
>>> string the error even refers to, let alone which parts of that
>>> string were
>>> invalid. In any case, it really shouldn't take five seconds of hard CPU
>>> crunching to detect and report an invalid input string.
>
> There's some more discussion at
> http://sourceware.org/bugzilla/show_bug.cgi?id=10948
>
> Installing the fonts font-isas-misc, font-jis-misc and
> font-daewoo-misc should also work around the problem, which can also
> be seen with other applications, as that ensures that at least one
> font exists for every charset.
>
> I agree that the error message sucks and should tell you the charsets
> which are missing and what string it was attempting to convert.
>
>> This topic came up last year, iirc the issue was this:
>>
>> http://invisible-island.net/xterm/xterm.faq.html#slow_menus
The xterm FAQ's workaround (setting LANG=C) indeed works, but then I
lose all of UTF-8, including some of the punctuation marks man pages and
gcc errors like to use.
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?
Regards,
Ryan
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Missing charsets in String to FontSet conversion
2010-08-03 15:21 ` Ryan Johnson
@ 2010-08-09 20:12 ` Jon TURNEY
2010-08-09 21:20 ` Ryan Johnson
0 siblings, 1 reply; 9+ messages in thread
From: Jon TURNEY @ 2010-08-09 20:12 UTC (permalink / raw)
To: cygwin-xfree
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Missing charsets in String to FontSet conversion
2010-08-09 20:12 ` Jon TURNEY
@ 2010-08-09 21:20 ` Ryan Johnson
0 siblings, 0 replies; 9+ messages in thread
From: Ryan Johnson @ 2010-08-09 21:20 UTC (permalink / raw)
Cc: cygwin-xfree
On 8:59 PM, Jon TURNEY wrote:
> 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.
>
Hi Jon,
Fortunately (for me, not for the bug hunt) I picked up the newer version
of xterm at some point, which set the menu locale to "C" and ended the
problems.
Thanks,
Ryan
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Missing charsets in String to FontSet conversion
2010-08-03 13:35 ` Jon TURNEY
2010-08-03 13:46 ` Andy Koppe
2010-08-03 15:21 ` Ryan Johnson
@ 2010-08-03 15:32 ` Ryan Johnson
2 siblings, 0 replies; 9+ messages in thread
From: Ryan Johnson @ 2010-08-03 15:32 UTC (permalink / raw)
To: cygwin-xfree; +Cc: Jon TURNEY
On 8/3/2010 3:35 PM, Jon TURNEY wrote:
> On 03/08/2010 10:00, Thomas Dickey wrote:
>> This topic came up last year, iirc the issue was this:
>>
>> http://invisible-island.net/xterm/xterm.faq.html#slow_menus
Oops... missed the other workaround to set XTerm.menuLocale:C in my
.Xresources file. All is well now.
Thanks!
Ryan
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2010-08-09 21:20 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-03 8:58 Missing charsets in String to FontSet conversion 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
2010-08-09 21:20 ` Ryan Johnson
2010-08-03 15:32 ` Ryan Johnson
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).