Mercurial > pidgin.yaz
view po/README @ 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 | ebf3b709a77a |
children | fd4630204ad5 |
line wrap: on
line source
Translation README Updated: 04-October-2003 ------------------ Translated .po files may be submitted in whatever native encoding is most convenient (and hopefully canonical). Please ensure that the Content-type: line reflects the proper character set. Updated: 19-April-2003 ------------------ To supply a new translation, you first need a copy of gaim.pot. This can be built by typing: ./update.pl --pot from the gaim/po/ directory. To update an exsting translation, type: ./update.pl LANG where LANG is the language code to update, such as fr or ja. This will build a new gaim.pot and update the translation with the changes. You may then begin editing the updated file. New or updated translations should be sent to the gaim-devel listserv (see http://lists.sourceforge.net/lists/listinfo/gaim-devel) Please check your translations carefully. Make sure you have the same number of newlines and %s or other formatting codes in the translation as you have in the original. Updated: 05-August-2003 ------------------ Before submitting updated or new translations, please run the following command to ensure the file does not contain errors: > msgfmt -c --statistics xx.po The comments at the top of each .po file should appear as follows: # Gaim Xxxxx translation # Copyright (C) 2002, Another Name <email@something.com> # Copyright (C) 2003, Your Name <email@whatever.com> # # This file is distributed under the same license as the Gaim package. # Thank you for flying Valu-Jet.