Mercurial > pidgin.yaz
view po/README @ 8672:142108e89399
[gaim-migrate @ 9424]
"This patch contains two fixes. The first is rather trivial, just removes
the declaration of extra pointer used for deleting a message and
deletes the message directly.
The second is the real bug that needed fixing.
Short Explanation:
The old code only fixed the message that was being displayed, and
still sent the original unchecked message to the receiving party. All I
did was add a handler to the load_plugin function to make it fix the
message being sent as well.
Longer Explanation:
In my cursory look through the gaim code (warning, <15 minutes) it
appears the message pointer send to all the various *-im-msg and
*-chat-msg handlers is a copy of the original string each time. This
means if you fix the string at one stage (displaying), you have to fix it
again at the next (sending). This seems rather inefficient, but hey, it's
your client, maybe it was a design feature.
Anyway, the spellchk plugin was only fixing the displayed
message, and not the message being sent. So I thought my messages
were being fixed while those receiving them new I was screwing up. I
added substitute_somethingorother handler for the sending-im-msg
callback in the load_plugin function.
Other comments:
I didn't look to deeply into it since it's so late, but the
"displaying-chat-msg" and "sending-chat-msg" callbacks appear to
be broken. The spellchk.c currently has a handler registered for the
first callback, but the message displayed on my screen still contains
the original typos. If I try to register a handler for the second callback
listed, Gaim crashes when sending the message to a chat window. As
I said, I didn't look into why it was crashing, I just removed my
attempt to handle it and built this patch." --Matt Brenneke
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Fri, 16 Apr 2004 14:39:34 +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.