On Thu, Jun 9, 2011 at 4:51 PM, Tim Mann <[email protected]> wrote:

> On Thu, Jun 9, 2011 at 4:04 AM, h.g. muller <[email protected]> wrote:
>
>> It is very inconvenient that the browser now doesn't work at all, though.
>> Perhaps we can overrule the resource-database setting for this single
>> useStringInPlace widget, and set international = False there, for the time
>> being.
>>
>
> Agreed, it's not acceptable for the browser to be completely broken. The
> approach you mention should work. I didn't get it to work last night, but I
> think I know what I was doing wrong. I'll try again probably tonight (in my
> time zone).
>

I couldn't get the approach of setting international = False only in the
browser widget tree to work. I kept getting segfaults deep inside Xlib. I
think Xlib gets confused by the mixture of internationalized and
non-internationalized widgets and ends up smashing memory somewhere by
confusing a char* with a w_char*. But I didn't really dig into it.

Instead I went ahead and internationalized the file browser. It seems to
work fine now, though I only tested it on a filename with German characters
in it. The diffs were surprisingly small.

I've pushed the change into savannah.

  --Tim
_______________________________________________
Bug-XBoard mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-xboard

Reply via email to