I've just pushed a git commit that fixes this issue. It was a few hours work
to get it all working 100% and avoid having libXt spit out "Warning: Missing
charsets in String to FontSet conversion" when xboard was started, but not
too bad.

I also fixed a couple of other tiny problems that I noticed, in separate
commits.

On Wed, May 18, 2011 at 7:13 PM, Tim Mann <[email protected]> wrote:

> Yes, that should do it. The default font is certainly a small change. I
> didn't look at the rest for very long, just enough to know it would take
> more time than I wanted to spend before going to bed. :-)
>
> On Wed, May 18, 2011 at 5:57 AM, h.g. muller <[email protected]> wrote:
>
>>  At 22:42 17-5-2011 -0700, Tim Mann wrote:
>>
>> It looks like we need to change FindFont to just return the fontset, then
>> change the rest of the code to set fontSet resources using that value
>> instead of setting font resources.  That looks like it will be a fair amount
>> of work to carry through fully. Maybe it's best to nuke all the old code in
>> the process instead of trying to carry it around and make it still work if
>> compiling without ENABLE_NLS defined.
>>
>>
>> Would this really require a lot of work? The current version uses 3 fonts:
>> clocks, board coordinates, and the rest. clockFont is used in only two
>> widgets, which explicitly mention an XtNfont arg at their creation. The
>> coordFont is only used for rendering text in the graphical board widget, for
>> which it is turned into a GC (coordGC). All the other stuff seems to be
>> handled in bulk, by the single call:
>>
>>     XrmPutStringResource(&xdb, "*font", appData.font);
>>
>> Couldn't we simply change that call to
>>
>>     XrmPutStringResource(&xdb, "*fontSet", fntSet);
>>
>> to acheive what we want? (And of course make sure fntSet used in FindFont
>> is a global variable.)
>> _______________________________________________
>> Bug-XBoard mailing list
>> [email protected]
>> https://lists.gnu.org/mailman/listinfo/bug-xboard
>>
>
>
_______________________________________________
Bug-XBoard mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-xboard

Reply via email to