<URL: http://bugs.freeciv.org/Ticket/Display.html?id=40006 >

#: server/unittools.c:2143
#, c-format
msgid "You found %d gold."
msgstr "金%dを見つけました。"

static void hut_get_gold(struct unit *punit, int cred)
  struct player *pplayer = unit_owner(punit);
  notify_player(pplayer, punit->tile, E_HUT_GOLD,
                   _("You found %d gold."), cred);
  pplayer->economic.gold += cred;

This is very bizarre and almost certainly the same as PR#40007.  The
strings look fine (in PR#40007 also) and the code looks fine.  There's a
very good chance it's caused by windows printf problems in combination
with utf-8.  If that is the case, then there is a very good chance using
libutf8 (which has its own printf) would fix it.  Use of libutf8 was
added in PR#12932 but removed in PR#36496, afaict.  So if someone on
windows has the time, apply this patch and re-compile with
--with-libutf8=yes on your configure.  If anyone can test this on other
platforms (or walk me through setting up locales, which have
mysteriously stopped working again) that would also be good.


Index: configure.ac
--- configure.ac	(revision 14241)
+++ configure.ac	(working copy)
@@ -372,6 +372,18 @@
   AC_DEFINE_UNQUOTED(LOCALEDIR, "./share/locale", [Locale directory (windows)])
+dnl Check libUTF8
+            AC_HELP_STRING([--with-libutf8],
+               [Use the libutf8 library (needed for some systems)]),
+            [with_libutf8=$withval], [with_libutf8=no])
+if test "$MINGW32" = yes || test "$with_libutf8" = yes; then
+  AC_CHECK_HEADER(libutf8.h, [],
+                  AC_MSG_ERROR([Could not find libutf8 library (libutf8.h)]))
+  AC_DEFINE(HAVE_LIBUTF8_H, 1, [Use libutf8's stdio functions])
+  LIBS="$LIBS -lutf8"
 dnl Check for zlib (needed for libpng)
 AC_CHECK_LIB(z, gzgets, , 
   AC_MSG_ERROR([Could not find zlib library.]), )
Index: utility/support.h
--- utility/support.h	(revision 14241)
+++ utility/support.h	(working copy)
@@ -26,6 +26,9 @@
 #include <sys/types.h>
+#ifdef HAVE_LIBUTF8_H
+#include <libutf8.h>
 #ifdef TRUE
 #undef TRUE
Freeciv-dev mailing list

Reply via email to