OK, I am back from Greece, so I had access to my Linux system again.
I started pushing all the WinBoard fixes I had accumulated in the mean time
to hgm.nubati.net (hgmaster branch), after syncing with Savannah.
There seems to e a problem, though, with the file browser. I suspect this
is a side
That's a feature that HG ported from winboard. The sizeNNN: in front
says use this font only for square size NNN. If you don't have the
sizeNNN:
there, xboard will use the font for whatever the current square size is.
But
when it saves settings, it saves the fonts only for the current
I learned a bit more, but progress is slow. Here are some observations:
* I was able to fix the slightly broken ru.po file that we have and get
the Russian translation to work. I didn't really know what I was doing; I
just did make ru.gmo and made likely-looking changes in places where I was
Thanks for the replies.
The first thing to realize here is that because we're using old Xaw widgets
and the old X core fonts mechanism, nothing is going to work great.
Everyone's effort for years has been to make the new Xft font mechanism work
well, convert programs to use it, and make nice
Basically this happens because the helvetica fonts that xboard uses by
default don't have Cyrillic characters, at least not the versions of those
fonts that you and I have on our machines. (I think we are both using some
release of Ubuntu, right? I'm using 10.04.)
I don't understand why we get
Update of bug #33241 (project xboard):
Status: Ready For Test = Fixed
___
Follow-up Comment #12:
After some more emails, it seems that that Auguste's main issue was just that
helvetica is not
Update of bug #33241 (project xboard):
Open/Closed:Open = Closed
___
Reply to this item at:
http://savannah.gnu.org/bugs/?33241
___
I pushed a commit that uses fixed as a fallback font for missing charsets.
It's ugly in large sizes (particularly the clocks), but at least it works.
A nice (?) side effect of this commit is that fixed also will be used as a
fallback when the user doesn't have helvetica installed at all. Everyone
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.
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 h.g.mul...@hccnet.nl wrote:
At 22:42 17-5-2011
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
Follow-up Comment #6, bug #33241 (project xboard):
found some reference on the web:
http://www.gentoo.org/doc/en/utf-8.xml
section KDE, GNOME and Xfce. It seems that you need to use a font that
fits:
-misc-fixed-*-*-*-*-*-*-*-*-*-*-iso10646-1
that is, you need a iso10646 encoding for Xaw to
Follow-up Comment #5, bug #33241 (project xboard):
hmm, I just tried it again on my computer and can't reproduce this...
LANG=en_US.utf8 as well as LANG=de_DE or no LANG settings works just fine...
which will make this harder to debug :(
At the moment I think this might be a font-related
Update of bug #33241 (project xboard):
Severity: 3 - Normal = 4 - Important
Status:None = In Progress
Assigned to:None = apersaud
Follow-up Comment #1, bug #33241 (project xboard):
Presumably this worked for Arun on his system before he checked it in. Could
you say exactly what linux (or other unix) distro you are on? What does
gettextize --version say on your system?
I had a different problem: I'm on Ubuntu 10.04 with
At 16:35 6-5-2011 +, Tim Mann wrote:
I had a different problem: I'm on Ubuntu 10.04 with gettext-tools 0.17, but
Arun checked in stuff built with 0.18. When trying to build, I got an error
about Makefile.in.in being the wrong version until I did this:
gettextize -f
./autogen.sh
./configure
Follow-up Comment #2, bug #33241 (project xboard):
i am on archlinux. gettext is version 0.18.1.1, although gettextize --version
only reports 0.18.1
gettextize -f before ./autogen.sh does not help. i also tried to copy
/usr/share/gettext/gettext.h into xboard directory, aclocal -I m4, autoconf,
Follow-up Comment #3, bug #33241 (project xboard):
I think this error can show up, if you use a font that doesn't support all the
characters needed for the locale you are using...
Some questions:
What language setting are you using when starting xboard with nls enabled?
Any warnings during the
23 matches
Mail list logo
