https://bugzilla.novell.com/show_bug.cgi?id=705238 https://bugzilla.novell.com/show_bug.cgi?id=705238#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dickey@his.com --- Comment #1 from Marcus Meissner 2011-07-14 12:04:28 UTC --- Wonder why it loads them as iso10646-1. I see 4MB transfered per start of xterm when running "ssh -v". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=705238 https://bugzilla.novell.com/show_bug.cgi?id=705238#c3 --- Comment #3 from Christopher Yeleighton 2011-07-14 17:05:18 UTC --- Note that replacing those entries with something else does not help; the only difference is that xterm loads "Misc-Fixed" instead of "misc-fixed". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=705238 https://bugzilla.novell.com/show_bug.cgi?id=705238#c5 --- Comment #5 from Thomas Dickey 2011-07-15 11:06:54 UTC --- xterm preloads fonts when it's necessary to compute the order for shifted keypad plus/minus. But at start-up - I don't recall that there's a path where it would do that. A quick check with xterm's trace for example shows only "fixed" being loaded - once. The replacement of the ISO-8859-1 "fixed" font with ISO-10646-1 is certainly a factor (no valid justification was given for that, of course). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=705238 https://bugzilla.novell.com/show_bug.cgi?id=705238#c7 --- Comment #7 from Christopher Yeleighton 2011-07-15 11:48:24 UTC --- Note that we can go with ISO-10646-1 fonts when we assume that the font is monospaced; that should save us from having to perform a full query. The network bandwidth can be reduced by using client-side font subsets instead (via libXft). Our incarnation of xterm supports libXft (requires using *facetName instead of *font). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=705238 https://bugzilla.novell.com/show_bug.cgi?id=705238#c9 --- Comment #9 from Thomas Dickey 2011-07-15 23:19:25 UTC --- hmm - taking more time to look. It's the encoding that is the issue. I'm used to considering "uxterm" to be the normal way that utf-8 encoding is used. Using ltrace, I see that if xterm uses utf-8 encoding, it makes 10 calls to XQueryLoadFont. ltrace shows enough context to see which fonts are being loaded, e.g., 1) nil2 (which "should" be a small font), 2) fixed 3) a request for a bold version of "fixed", which is 8859-1 4) double-width medium 10646 5) double-width bold 10646 6) the "font" value from UXTerm app-defaults, which is 10646-1 7) a 10646 version of #3 8) same as #4 9) same as #5 10) unknown (context doesn't show a string) The basic reason why it's preloading those is so that it can refer to GC's for each. I can probably improve on the caching, e.g., so that 3-5 and 7-9 weren't accessed immediately (the caching work that I did a couple of years ago simply didn't go far enough). Still, that's only a factor of 2-3 over where it is now - so you'd be downloading a megabyte. Using Xft doesn't affect that much, unless xterm is unable to find the bitmap fonts - in that case it relies only on "fixed". Thinking about _that_, I've already modified it to work with just Xft. Another configuration tweak would allow it to ignore bitmap fonts. Then you'd only have Xft to be concerned with. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=705238 https://bugzilla.novell.com/show_bug.cgi?id=705238#c11 --- Comment #11 from Thomas Dickey 2011-07-16 11:28:32 UTC --- I did add the last item to my to-do list (to add a resource setting to help in this area). So it might appear in #272. Addressing the middle part (reducing the fonts needed by xterm for UTF-8 mode) is stickier since there are probably places where xterm loads a font to check on its size. Some of that can be deferred - needs some investigation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.