Re: Character encoding in KMail

On Tuesday 03 February 2009, Anne Wilson wrote:
> On Tuesday 03 February 2009 19:26:11 Ingo Klöcker wrote:
> > On Tuesday 03 February 2009, Anne Wilson wrote:
> > > On Tuesday 03 February 2009 19:02:30 Ingo Klöcker wrote:
> > > > On Tuesday 03 February 2009, phep wrote:
> > > > > Anne Wilson a écrit :
> > > > > > A new development for me is that when I reply to some
> > > > > > messages I get a warning about characters that can not be
> > > > > > displayed, and asked whether to drop the characters or
> > > > > > change the encoding.  I have looked over the messages in
> > > > > > question and don't see anything unusual about them.  Can
> > > > > > anyone tell me more about this?
> > > > > >
> > > > > > I can see the use where there are obvious character
> > > > > > problems, even though I can't recognise the problem with
> > > > > > regard to Kishore's messages to [email protected] which is
> > > > > > where the problem is now showing up.
> > > > >
> > > > > This probably happens when you reply to messages which are in
> > > > > a different encoding from your's and you quote all or part of
> > > > > them.
> > > > >
> > > > > E.g. you receive a ISO-8859-X encoded message and you reply
> > > > > to it with your default UTF-8. What KMail asks you then is
> > > > > probably what to do whith the non-ascci characters of the
> > > > > quoted message : convert them to UTF-8 so that your message
> > > > > shall keep coherent (albeit converting the original quoted
> > > > > charcaters) or else ... not displaying those non-ascii
> > > > > ISO-8859-X characters since there can't be, logically, 2
> > > > > distinct charsets in the same piece of code !
> > > > >
> > > > > Note that this is just a guess, Ingo will probably correct
> > > > > ;-)
> > > >
> > > > AFAIK, KMail will not ask you if there's an encoding in the
> > > > list of preferred encodings (under Composer/Charset in the
> > > > settings dialog) which is a superset of the encoding used for
> > > > the received message. It is advisable to put utf-8 into the
> > > > list of preferred encodings because utf-8 is a superset of all
> > > > encodings. I think by default the list consists of two
> > > > encodings: your local encoding and utf-8.
> > >
> > > My local encoding is utf-8, so that should be straight-forward.
> > >
> > > > Kishore's first reply in the "What happened to 'Find in
> > > > message'?" thread contains the character 0xA0 (in hex notation)
> > > > in the quote of Anne's message. I have no idea why KMail seems
> > > > to have replaced the two space characters in "[...] the same
> > > > job.  Was [...]" with a space followed by 0xA0. Could be a bug.
> > > >
> > > >
> > > > BTW, using KMail 1.9.10, I didn't get an encoding message when
> > > > replying to Kishore's message and the 0xA0 did end up correctly
> > > > in my reply. OTOH, in Anne's reply the 0xA0 was replaced by a
> > > > '?' (question mark). I'll retry with KMail 1.11 when I have
> > > > finally switched to KDE 4.2.
> > >
> > > I've never seen these encoding messages until today.  I've got a
> > > total blank on where general encodings are set - I though it was
> > > Region & Language - but I'm pretty certain I set utf-8.  All the
> > > same, I'd like to check it, if I can find it.
> >
> > In KMail 1.9.10 it's in Composer/Charset in the settings dialog.
> > Obviously, those encodings are KMail specific.
>
> Yes, I know about them - but I thought that there was another place
> that I set encodings.  Perhaps not.  Anyway, that's set to
> auto-detect,  Do you recommend changing it to utf-8?

I don't think we are talking about the same thing. I'm talking about the 
Charset page of the Composer settings in KMail's configuration dialog. 
There is no "auto-detect" there (in KDE 3.5 anyway).


Regards,
Ingo

_______________________________________________
KDE PIM users mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkmIwA0ACgkQGnR+RTDgudhMPQCeJyRE6KdxqEg4wlVTHlkJxr+f
F8UAoL8gWI+3Wdo4ZwT4kszcDh+fmfrY
=Gwsm
-----END PGP SIGNATURE-----