view po/README @ 8986:8cf32769ba1b

[gaim-migrate @ 9761] " This patch adds a Plugin Actions menu item after the Account Actions menu. The Plugin Actions menu is populated from the added 'actions' slot in GaimPluginInfo. As a demonstration, the Idle Maker plugin has been converted to no longer require GTK code and the Preferences interface just to perform its actions. Instead, it uses a Plugin Action to spawn a Fields Request. There's also a minor fix for consistency in the menu building for buddy actions. The pre-existing method for instructing a menu list to display a separator was to insert a NULL rather than a proto_buddy_menu into the GList of actions. The code for the buddy menus was instead checking for a proto_buddy_menu with a '-' label. This has been fixed, and it now correctly uses NULL to indicate a separator." "Date: 2004-05-16 02:25 Sender: taliesein Logged In: YES user_id=77326 I need to add a callback to this patch to watch for loading/unloading of plugins (to determine when to rebuild the menu). Since the appropriate way to handle Plugin Actions is still mildly up for debate, I'm holding of on correcting the patch until I know for sure whether I should fix this patch, or scrap it and write a new one using a different method." "Date: 2004-05-18 12:26 Sender: taliesein Logged In: YES user_id=77326 I've completed changes to this patch to also add plugin load and unload signals (it looks like plugin.c actually had pre-signal callbacks in place, but they were never used or converted to signals) This patch now will correctly update the Plugin Action menu as plugins load and unload." I'm not entirely sure i like the ui of a plugins actions menu, but i think that having some way for plugins to add actions on an account is a good thing, and i'm not sure that every viable action fits under the accounts actions menu. we may want to merge the two (the existing accounts actions and this plugins actions), but both times it came up in #gaim no one seemed to want to comment, and on one commented to the gaim-devel post either. 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.