[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 60549] New: kmail composer with external editor botches
From:       Alain Knaff <kde () alk ! org ! lu>
Date:       2003-06-30 18:15:18
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=60549     
           Summary: kmail composer with external editor botches character
                    set encoding
           Product: kmail
           Version: 1.5.1
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kmail@kde.org
        ReportedBy: kde@alk.org.lu


Version:           1.5.1 (using KDE 3.1.2)
Installed from:    SuSE
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.21

While composing, Kmail misdisplays Euro Signs as "crossed circle", even after \
selecting iso-8859-15 as the encoding.

When attempting to send the mail, it pops up a cryptic error message ("Not all \
characters fit into the chosen encoding. Send the message anyway?"), and upon \
clicking yes, the euro-signs are replaced with question marks (ascii 63). Please fix \
this.

N.B. This is not the only character set issue in KDE 3.1.2 . In many other apps, \
setting up default character encodings has become increasingly difficult, or \
sometimes buggy. I remember that in previous versions this has been a lot easyer.

N.B. The problem has been observed when using emacs (or rather: gnuclient) as an \
external editor. Emacs shows the euro sign correctly. Only after Ctrl-X # is it shown \
as the infamous iso-8850-1 crossed circle in kmail.

When switching off external editor, kmail shows a blank square instead of Euro.

> From what I've heard, KDE is trying to use some kind of "smart" autodetection to \
> guess what the user wants, but it seems in many situations this does not work out. \
> Please provide a (working) option to allow the user to say explicitly what he \
> wants.
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail


[prev in list] [next in list] [prev in thread] [next in thread]