Bug 45288

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 16 July 2002 11:17 e.maryniak@pobox.com wrote:
> However when I forward or redirect (Message|Forward
> Message|Redirect) an existing message (that has long
> lines) KMail _does_ word wrap the forwarded or
> redirected message (at column #78 by the way).
>
> This is can be annoying when forwarding SuSE
> security announcements with long ftp url's that
> are now broken at the '.rpm' point!

Simply forward messages as attachments if you don't want them to be 
altered.

> A workaround _would_ have been to set the '78' number
> to a higher one (e.g. 130 or 254) but 78 also seems
> to be a hard built-in limit...

That's right.

Regards
Ingo

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

iD8DBQE9Nz+fGnR+RTDgudgRAjauAKCIqKbTG553neLwro0T1sv9UXfxuQCg0eTL
MsYZcjj6G35C9S3XkZfe3Aw=
=hN8l
-----END PGP SIGNATURE-----

On Friday 19 July 2002 00:22 Ingo Kl=F6cker wrote:
> On Tuesday 16 July 2002 11:17 e.maryniak@pobox.com wrote:
> > However when I forward or redirect (Message|Forward
> > Message|Redirect) an existing message (that has long
> > lines) KMail _does_ word wrap the forwarded or
> > redirected message (at column #78 by the way).
> >
> > This is can be annoying when forwarding SuSE
> > security announcements with long ftp url's that
> > are now broken at the '.rpm' point!
>
> Simply forward messages as attachments if you don't want them to be
> altered.

Hmm I see with shift-F that's quite handy!
However just out of curiosity I wonder is there a design philosophy
why messages forwarded as text are altered (namely wrapped) and not
left as be? You may note that:

- PGP/GPG signed message parts therein might fail when their
  message signature/checksum is checked.
- The wrapping even occurs when the [ ] Word wrap option is
  disabled i.e. explicitly suppressing word wrap by the user
  is overruled by the program when it comes to forwarding messages
  as text; imho suppressing word wrap should apply to them too.
  When a user puts the wordwrap button on the toolbar he or she
  can always wrap later if he or she re-decides.

Bye-bye

Eric

> > A workaround _would_ have been to set the '78' number
> > to a higher one (e.g. 130 or 254) but 78 also seems
> > to be a hard built-in limit...
>
> That's right.
>
> Regards
> Ingo
>
>
> (Complete bug history is available at http://bugs.kde.org/db/45/45288.htm=
l)

--=20
Eric Maryniak <e.maryniak@pobox.com>
WWW homepage: http://pobox.com/~e.maryniak/
Mobile phone: +31 6 52047532 or (06) 520 475 32 in NL.

Why does everyone always overgeneralize?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 22 July 2002 10:42 Eric Maryniak wrote:
<snip>
> > Simply forward messages as attachments if you don't want them to be
> > altered.
>
> Hmm I see with shift-F that's quite handy!
> However just out of curiosity I wonder is there a design
> philosophy why messages forwarded as text are altered (namely
> wrapped) and not left as be?
<snip>

The philosophy is to get people to use forward as attachment since - as=20
you correctly noted - the inline method is broken by design for=20
anything more than trivial messages. To this end we've made forward as=20
attachment the default for KDE3.1 and switched the hotkeys between=20
inlined and attached. ;-)

With redirect you are right. This shouldn't even bring up the composer=20
or if it does it should disable the editor. It should add it's=20
Resent-* headers to the original message and send that without any more=20
changes. I guess this is a duplicate of another wish/bug report so=20
together with the above I'm closing this report (if it's not already=20
closed)

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

iD8DBQE9O9aQ3oWD+L2/6DgRAqkOAKCmYanr65r8s2RB5gEjZmrQHfZVjACgjE1+
KMKEMxiknmSz4F4JaCCA7VQ=3D
=3DG0dr
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 22 July 2002 10:42 Eric Maryniak wrote:
> Hmm I see with shift-F that's quite handy!
> However just out of curiosity I wonder is there a design
> philosophy why messages forwarded as text are altered (namely
> wrapped) and not left as be? You may note that:
>
> - PGP/GPG signed message parts therein might fail when their
>   message signature/checksum is checked.

If you want to forward a message unaltered then forward it as 
attachment.

> - The wrapping even occurs when the [ ] Word wrap option is
>   disabled i.e. explicitly suppressing word wrap by the user
>   is overruled by the program when it comes to forwarding messages
>   as text; imho suppressing word wrap should apply to them too.
>   When a user puts the wordwrap button on the toolbar he or she
>   can always wrap later if he or she re-decides.

This is indeed a bug. But it has already been reported before.

Regards
Ingo

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

iD8DBQE9PIEbGnR+RTDgudgRAhQOAJ9WpSEPKuYd43G47Lr6w02WIBO5XgCfRqhd
B7eVrwLyXTFww26XgQ2IqEY=
=7eGb
-----END PGP SIGNATURE-----

This bug is CLOSED, but not really fixed. I would like to reopen it 
because it seriously impairs usability for my usage pattern. 
 
As a developer, I usually work with patches via e-mail. When I 
forward a patch with KMail, it gets wrapped and destroyed. 
 
Forwarding as attachment is not an option for patches since it's 
rude to most developers who use different mail clients and want 
to quickly see the patch and being able to apply it after saving 
the verbatim message. 
 
KMail's policy should be not touching anything in the body of 
forwarded or redirected messages. Any mail client who dares 
altering message text when not asked to is just annoying 
because it's trying to outsmart the user like Microsoft software does.