[Super-tux-commit] supertux configure.ac,1.43,1.44 TRANSLATORS,1.8,1.9

[Matze B. <mat...@us...>]

Update of /cvsroot/super-tux/supertux
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19530

Modified Files:
	configure.ac TRANSLATORS 
Log Message:
check in configure if xgettext supports lisp

Index: configure.ac
===================================================================
RCS file: /cvsroot/super-tux/supertux/configure.ac,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- configure.ac	10 Dec 2004 21:52:13 -0000	1.43
+++ configure.ac	14 Dec 2004 09:43:38 -0000	1.44
@@ -28,6 +28,16 @@
 AC_PROG_INSTALL
 
 AC_CHECK_PROGS(XGETTEXT, xgettext)
+if test -n "$XGETTEXT" ; then
+    AC_MSG_CHECKING([if xgettext supports lisp])
+    if echo '(gettext "test")' | xgettext -o - -L Lisp - >& /dev/null; then
+        AC_MSG_RESULT(yes)
+    else
+        AC_MSG_RESULT(no)
+        AC_MSG_WARN([It seems your gettext installation is too old, try updating it])
+        XGETTEXT=""
+    fi
+fi
 
 dnl Checks for header files.
 AC_HEADER_DIRENT

Index: TRANSLATORS
===================================================================
RCS file: /cvsroot/super-tux/supertux/TRANSLATORS,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- TRANSLATORS	6 Dec 2004 17:59:34 -0000	1.8
+++ TRANSLATORS	14 Dec 2004 09:43:38 -0000	1.9
@@ -4,7 +4,8 @@
 * Install gettext
 * get a cvs snapshot of supertux and do the usual autogen.sh, configure.
   Make sure configure can find the xgettext application.
-    (ie. "checking for xgettext... xgettext")
+    (ie. "checking for xgettext... xgettext"
+     and "checking if xgettext supports Lisp... yes")
 * Run 'jam' and let it compile supertux and create all the messages.po files
 * Go into data/locale and data/levels/*/ and in each dir do:
      - In case you want to create a new translation do