Re: KMail and characters sets (=20 problem)

On Wednesday 16 March 2011 08:16:32 Ingo Klöcker wrote:
> On Tuesday 15 March 2011, Peter wrote:
> > On Tuesday 15 March 2011 08:29:22 Ingo Klöcker wrote:
> > > On Monday 14 March 2011, Peter wrote:
> > > > Some emails being sent from KMail refuse to use the char set
> > > > defined.
> > > > 
> > > > Some lines end in = , and then the next line starts in =20
> > > > and there are a whole lot of lines with "=20" in them.
> 

[snip]

> > Okay, my concern was continuing along the lines of what i saw in the
> > 'save as', and didn't want that sort of 'garbage' being 'seen' by
> > the recipients. However, if you are 100% certain that people will
> > not see it, but only see the plain text (non-html anyway), then that
> > is okay.
> 
> I'm 99% certain. There will always be people using totally crappy mail
> clients (web mail clients come to mind, or primitive mail clients on
> mobiles) that will see the encoded characters. But everybody else will
> see your messages correctly. Even people using a mail client from
> Microsoft. :-)

Okay, thanks. I'm not going to worry about the encoding showing.
 
> > Anyway, I will leave it on 'auto etect' as it has been
> > 
> > Under Composer, Charset TAB, the order is
> > 
> > iso-8859-1
> > us-ascii
> > utf-8 (locale)
> > utf-8
> > 
> > but I guess 'auto detect' overrides that.
> 
> No, it does not override that. In fact, 'auto detect' tries those
> charsets from top to bottom to find a suitable charset. BTW, you might
> want to move us-ascii before iso-8859-1. Otherwise, us-ascii will never
> be used (because iso-8859-1 is a superset of us-ascii).

I have done as you advised, thanks.
 
> > One area that did give me
> > concern though, is when KMail was 'forced' to (say) us-ascii, a msg
> > appears like 'chars will be lost', I press okay amd send, but email
> > seems okay. However, if I wait a few more seconds, the email in
> > composer mode turns out complete rubbish, all formatting is lost,
> > many characetsr have been changed, etc.
> > 
> > So, what I'm saying is, if I do use "force" the encoding, I have to
> > send it within a few seconds, otherwise the whole email is
> > clobbered, but at least the 'edit undo' is there.
> 
> Hmm. Obviously, this should not happen. Please submit a bug report via
> Help->Report Bug.

Hmm, now I can't replicate it, ..bother. Maybe because I moved us-ascii 'up' a 
notch, I don't know.
 
> > I wonder what this will be sent as, there are no special chars, so
> > us-ascii should be okay.
> 
> Actually, there is at least one special character in your message. In my
> last name which was included in your reply in the "On ... wrote" line.

Oh, yes I see, I missed that totally.

Thanks,

Peter
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users