Bug#438644: hex-a-hop: strange menu with russian translation

Jens Seidel jensseidel at users.sf.net
Sat Aug 18 18:12:00 UTC 2007


clone 438644 -1 -2
retitle -1 hex-a-hop: Russian translation
tags -1 +pending
severity -2 normal
thanks

Hi Yuri,

On Sat, Aug 18, 2007 at 07:23:12PM +0400, Yuri Kozlov wrote:
> While trying to translate this program in Russian

thanks, I committed this partial translation already. Once you
finished it please send an update to the bug report.

> I have a strange strings in the
> main menu.(several "% complete" in the same time)

Indeed, it should look differently (such as in the 3rd line of your
snapshot).

> And how to select another font?

I don't know it (yet). hex-a-hop uses Pango and fontconfig.
Searching for "Pango fonts" I found
http://people.redhat.com/otaylor/pango-mirror/xfonts.shtml
There should be a config file somewhere, where you can possibly define
some aliases. I you find a solution (e.g. how to use a bolder font
(without <b>...</b>)) please contact me.

You may also try (temporarily) to use translations similar to:
<span font_family="Courier New"><i>your translation.</i></span>

But why do you want to use another font? The default one (from your
screenshot) looks good, all characters are OK and readable.

(Titles in the help screen are not yet rendered properly. I will fix
it now.)

> Also running LC_ALL=C hex-a-hop give me a
> yuray at keeper:/tmp$ LC_ALL=C hex-a-hop
> Reading binary file "save4.dat" ("/home/yuray/.hex-a-hop/save4.dat")
> Warning: unable to open file "/home/yuray/.hex-a-hop/save4.dat" for reading
> Segmentation fault

Strange. Please first make a copy off all these files. If they are not
too large please attach these compressed.

Does it also happen if you use another locale? I see you use a 64 bit
system, probably that's the reason.

I have a 64 bit big endian system but it currently lacks a C++ standard
library, so I'm not sure that I'm able to test on such a machine soon.

> Architecture: amd64 (x86_64)

Please build the package from source using debugging information. Just
ensure that $DEB_BUILD_OPTIONS contains "nostrip":

# apt-get build-dep hex-a-hop
$ export DEB_BUILD_OPTIONS="$DEB_BUILD_OPTIONS nostrip"
$ dpkg-buildpackage -rfakeroot -us -uc

Can you maybe try to start hex-a-hop in valgrind (valgrind hex-a-hop) or
with strace?

Jens




More information about the Pkg-games-devel mailing list