view po/README @ 11719:109ee3bfeac5

[gaim-migrate @ 14010] SF Patch #1333770 from corfe83 "Many times in gaim we use the function g_slist_remove(list,node->data) to remove an element from a GSList. If we already have the pointer to the node we want to delete, it is faster to send it the pointer to the node to delete rather than the data of the node (we can do this by calling g_slist_delete_link(list,node)). This change was made while looking at glib's documentation and the code in glib's gslist.c. This is because as the remove/delete function traverses each node in the list, it doesn't need to spend an extra memory access to retrieve the data for each element in the node it is traversing and then compare, it can simply compare the pointer. In my tests outside of gaim, this makes a big difference if the node you are deleting is at a high index in the list. However, even if you're deleting the first node, it about breaks even. So, I've found each case in gaim where we are calling g_slist_remove, and we already have the pointer to the appropriate node to delete (this is often the case when we're doing a for or while loop on a GSList). I've then replaced it with the appropriate call to g_slist_delete_link. I, however, didn't do this in situations where we are explicitly removing the first element in the list, because in those situations it is an unnecessary change. There should be no difference in behavior, but just in case I've tried running it with valgrind, which reports the same number of memory leaks after my patch as before my patch. Of course, I can't guarantee that my normal behavior on gaim is hitting all the functions I've changed, but in general testing it Works For Me (tm)." As with the last patch, this one may not have a practical performance impact (or maybe it does, I have no idea), but it's not worse for any case. Given two ways of doing things where one is always at least as fast and may be faster under some cases, I like to prefer that faster way. This doesn't make the code any uglier, so I'm applying. 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.