--===============1171041240==
Content-Type: multipart/signed;
boundary="nextPart1339084.UhqCitTZV8";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
--nextPart1339084.UhqCitTZV8
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Le Dimanche 11 D=E9cembre 2005 20:01, Christian Parpart a =E9crit=A0:
> Hi,
>
> well, I'm still thinking (read: designing) on how to implement a Kopete
> plugin for my community server I wrote, however, this server actually
> submits already XHTML formatted chat messages to listening clients, as the
> only client software currently existing was an apache module.
>
> So, can I just pass them to kopete directly? I mean, a message could even
> contain a
or
and alike.
You can give to the Kopete::Message a XHTML formated body by specifying=20
RichText as format argument.
Anyway, be aware that the content will be passed dirrectly to KHTML without=
=20
being parsed at all.
Java and JavaScript are disabled. But not images, link, .... that will=20
appears as it. so there may be phishing problems. =20
> I'm a little bit worried about, because I took a look at the theming
> tutorial on kopete.org, and it just did (=
and
> not a xsl:apply-templates as it should be then)
>
> Thanks in advance,
> Christian Parpart.
--nextPart1339084.UhqCitTZV8
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQBDnHmgz58lY8jWrL0RAkVbAJ9dKgu2Z+NLzro0jN+HPHIrh5952gCcCDnP
4E/bpOJ+lmZeP3Atjq0gnaE=
=dAmP
-----END PGP SIGNATURE-----
--nextPart1339084.UhqCitTZV8--
--===============1171041240==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
--===============1171041240==--