Mercurial > pidgin.yaz
view autogen.sh @ 7724:613b20c69d2c
[gaim-migrate @ 8369]
this didn't cause me any problems yesterday, and it compiles, and bug fixing is a good thing.
"Some month ago I introduced translatable texts for "gaim --help" and
"gaim-remote --help".
Unfortunately the output of the translated text is often unreadable.
The problem is, that Gaim's *.po files have the UTF-8 locale (because
this is the default charset for GTK+ 2.0). But the users may have
configured other locales. For instance my SuSE Linux 9.0 system is
configured with LANG=de_DE@euro. "euro" is ISO-8859-1 (Western
character set, 8 Bit, with the Euro currency symbol). Lots of UTF-8
characters are unreadable if they are displayed in a 8 Bit charset
without conversion. Only the 7 Bit chars are displayed right.
There are two possible solutions:
1) Make the console texts untranslatable. This isn't very clever.
2) Convert the texts from UTF-8 to user's locale.
I choose the second solution.
The conversion cannot be made during the translation, because gettext
does not allow a mix of different character sets in one po-file.
My patch converts the console strings from UTF-8 to users locale.
Normally this works right, because most users have a locale which is
compatible with their language.
The case where a user uses a language (for instance German:
LANG=de_DE) with an incompatible character set (for instance the 7Bit
charset LC_CTYPE=C) is also handled. The user then sees a warning and
the original UTF-8 message.
At first I tried to make a new UTF-8 function in src/util.c. But the
function is needed 5 times in src/gaim-remote.c and 2 times in
src/main.c. gaim-remote is not linked against util.o. Also there are a
lot of dependencies from util.o to other files, so I will introduce a
lot of trouble to link gaim-remote against util.o.
So I only wrote a function in src/gaim-remote.c and used the UTF-8
conversion inline in src/main.c." --Bjoern Voigt
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Wed, 03 Dec 2003 13:21:55 +0000 |
parents | d881871490dd |
children | e67993da8a22 |
line wrap: on
line source
#!/bin/sh SETUP_GETTEXT=./setup-gettext ($SETUP_GETTEXT --gettext-tool) < /dev/null > /dev/null 2>&1 || { echo; echo "You must have gettext installed to compile Gaim"; echo; exit; } (libtoolize --version) < /dev/null > /dev/null 2>&1 || { echo; echo "You must have libtool installed to compile Gaim"; echo; exit; } (automake --version) < /dev/null > /dev/null 2>&1 || { echo; echo "You must have automake installed to compile Gaim"; echo; exit; } (autoconf --version) < /dev/null > /dev/null 2>&1 || { echo; echo "You must have autoconf installed to compile Gaim"; echo; exit; } echo "Generating configuration files for Gaim, please wait...." echo; # Backup the po/ChangeLog. This should prevent the annoying # gettext ChangeLog modifications. cp -p po/ChangeLog po/ChangeLog.save echo "Running gettextize, please ignore non-fatal messages...." $SETUP_GETTEXT # Restore the po/ChangeLog file. mv po/ChangeLog.save po/ChangeLog echo "Running libtoolize, please ignore non-fatal messages...." echo n | libtoolize --copy --force || exit; # Add other directories to this list if people continue to experience # brokennesses ... Obviously the real answer is for them to fix it # themselves, but for Luke's sake we have this. for dir in "/usr/local/share/aclocal" \ "/opt/gnome-1.4/share/aclocal" do if test -d $dir ; then ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I $dir" fi done aclocal $ACLOCAL_FLAGS || exit; autoheader || exit; automake --add-missing --copy; autoconf || exit; automake || exit; ./configure $@