Follow-up Comment #8, bug #33241 (project xboard):
here is the strace result get by strace -o strace.result xboard
i don't know how to read it, just provided it for you information.
http://paste.pocoo.org/show/390407/
___
Reply to this
Follow-up Comment #9, bug #33241 (project xboard):
after reading the strace output, which is quite cryptic to me, and considering
arun's earlier suggestion, i changed the last seven sections of all font
related specs into * in ~/.xboardrc. miraculously, xboard started.
the font were matched to
At 01:13 17-5-2011 -0700, Tim Mann wrote:
p.s. I just tried, and editing the .xboardrc file to change the fonts from
iso8846 to iso10646 did NOT fix the broken umlauts. So there is more to
that problem.
I don't really know anything about X-fonts, but apparently iso10646 and
such stands for
iso10646 in the font name means Unicode. It doesn't mean utf8, since that's
just a way of compressing a sequence of 32-bit Unicode code points into a
sequence of 8-bit bytes.
What we see happening in xboard is that something (maybe Xaw, but I'm not
100% sure) does not understand that the string
Hi
does anyone know of any other Xaw program that uses gettext? Perhaps we
can just check their code and see how they do it ;) I can't think of any
right now though, but will search a bit once I have some time on my hands...
Arun
___
Bug-XBoard
After some more random googling and flailing, I have learned that setting
the resource *international: True in Xaw widgets makes them do something
more nearly correct. Try this:
env LANG=de_DE.utf8 xboard -xrm '*international: True'
When I do that, I get correct umlauts and the ß character in
