view po/README @ 9460:eae7e049d639

[gaim-migrate @ 10285] " This patch completely eliminates the use of the old numeric prpl identifiers. I've noticed that some plugins (both in gaim's cvs and external) continue to use the constants even though they are essentially no longer valid - code that relies on them being unique will fail - the new built-in prpls (SILC and novell) ,and any recent external prpls don't have numeric values. The once side effect that the removal causes is that the code for importing of the old .gaimrc and *.blist files is a little more kludgy (using magic numbers instead of the old constants). IMHO this isn't a big deal as the code will go away eventually anyway. **This patch also fixes the raw plugin so that i compiles once again. **Someone should make sure that the gaim-remote and raw plugins still work. (If the raw doesn't work, it may be unrelated as it hasn't been updated since the latest significant MSN changes - i just made a minor change to make it compile)" --Daniel Atallah (13:44:44) Me: what think you of getting rid of prpl numbers? (13:45:05) Sean: what do you mean? (13:45:27) Me: right now they are listed as deprecated, but still used in a few of our own plugins as well as in some 3rd party stuff (13:45:32) Me: and the enum still exists in the core (13:45:44) Me: and the newwer prpls such as novell don't use them (13:45:59) Me: datallah has submitted a patch to get rid of them entirely (13:46:31) Me: the only thing it would break would be the old blist import, which he hacked into working with magic numbers, but which i tend to think we could remove entirely anyway (13:50:03) Sean: Let's get rid of them, then. (13:50:10) Sean: and take out old .blist code too (13:50:14) Me: cool (13:52:37) Sean: we should get rid of .gaimrc code too, sometime. (13:53:02) Sean: If anyone's seriously just now upgrading from 0.59.x, or whatever, they deserve to lose their preferences. (12:27:56) LSchiere: Paco-Paco: what do you think of getting rid of the deprecated prpl numbers? (12:28:14) Paco-Paco: LSchiere: I think it shouldh ave happened long ago committer: Tailor Script <[e-mail]>

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 <[e-mail]>
# Copyright (C) 2003, Your Name <[e-mail]>
#
# This file is distributed under the same license as the Gaim package.
#

Thank you for flying Valu-Jet.