view libpurple/purple-send-async @ 28449:7a211be81a6b

Strip off the outer <html> and <body> from iChat messages. Should Fix #9968. A recent fix in purple_markup_strip_html exposed an issue with iChat messages, since they contain an <html/> that is not the outermost element. Before, what was passed to libpurple looked like this: <font back="#E68CBD"><font color="#000000"><html><body ichatballooncolor="#E68CBD" ichattextcolor="#000000"><font face="Helvetica" ABSZ=12 color="#000000">message</font></body></html></font></font> Now, it looks like this: <font back="#E68CBD"><font color="#000000"><font face="Helvetica" ABSZ=12 color="#000000">message</font></font></font> Better than it was before? Yes. Worth fixing the fact there are 3 font tags? Probably not. My iChat friend is offline, but it worked properly when I tested this routine all by itself.
author Paul Aurich <paul@darkrain42.org>
date Wed, 26 Aug 2009 05:55:25 +0000
parents cea56d000b16
children
line wrap: on
line source

#!/bin/sh

METHOD_NAME=$1

if test -z "$METHOD_NAME"
then
    cat <<EOF
This program calls purple API functions using DBus.  As opposed to purple-send,
it does not print the return value.

Usage:

   $0 method-name type1:parameter1 type2:parameter2 ...

This shell script just invokes dbus-send, see man dbus-send for how
to specify the parameters.

Examples:

   $0 PurpleCoreQuit

Use dbus-viewer to get the list of supported functions and their parameters.
EOF
    exit 1
fi

shift
dbus-send --dest=im.pidgin.purple.PurpleService --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@"