--===============0050102503==
Content-type: multipart/signed; boundary=nextPart2108526.V6x9EseJ9F;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart2108526.V6x9EseJ9F
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 23 February 2007 18:33, David Faure wrote:
> On Thursday 22 February 2007, Ingo Kl=F6cker wrote:
> > > In my testing I noticed one strange behavior: inline-forwarding
> > > an HTML-only mail leads to html tags in the body of the composer
> > > window, but I think this is unrelated to my changes.
> >
> > That's by design. If the HTML message is viewed as HTML then the
> > HTML is converted to text, but if the HTML message is viewed as
> > plain text then the plain text is forwarded.
>
> Well, yes, but replying to an HTML-only message converts it to plain
> text so one might expect that forwarding it would do that too.
> I can see how that's different code paths internally though.

If you'd like to change this then go ahead. It doesn't make much sense=20
to keep the HTML tags when forwarding the text inside a plain-text=20
message.

Regards,
Ingo

--nextPart2108526.V6x9EseJ9F
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBF31nLGnR+RTDgudgRAvWMAKCKK9nzpNyXZzaEkkJJkw5KQRSlKgCfQLC1
jLxWUsptfLYSXK/Dzp/B4vs=
=xqi8
-----END PGP SIGNATURE-----

--nextPart2108526.V6x9EseJ9F--


--===============0050102503==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel

--===============0050102503==--