Re: Character encoding in KMail

Anne Wilson <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Message-ID <[email protected]>
On Tuesday 03 February 2009 11:59:41 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 ;-)
>
It's odd that I've never come across it before.  It's probably a setting that 
I have changed recently.  I'll dig around.

Anne

_______________________________________________
KDE PIM users mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-users
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkmIOyIACgkQbMErw/n0TZowdQCcCCw3AEdUWssOqF8376sW1HxL
YdwAn3QRR9h8kKqQO7yebi7cd71roGLR
=Be1T
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.