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

List:       kde-bugs-dist
Subject:    
From:       Ingo "Klöcker" <kloecker () kde ! org>
Date:       2003-04-11 8:59:54
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=57093     
kloecker@kde.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |wishlist
             Status|UNCONFIRMED                 |NEW
      everconfirmed|0                           |1
            Summary|kMail doesn't honor default |Add charset selection box to
                   |encoding of OS when         |Attach File dialog
                   |attaching vCards from files |



------- Additional Comments From kloecker@kde.org  2003-04-11 10:59 -------
KMail uses the encoding that is selected for the message. So the workaround is to select utf-8 
encoding before attaching the vCard. After attaching the vCard you can switch back to 
automatic encoding. 
 
The problem is that vCards don't have a charset entry. Instead the charset has to be provided in 
the attachment headers according to the RFC. But this makes it pretty much impossible to 
attach vCards which are stored in a file with the correct encoding because the vCard doesn't 
contain any information about the encoding. So it's impossible for KMail to know the charset 
which has been used to encode the vCard. AFAIK kaddressbook always uses utf-8 (which 
makes sense because then the difficult guessing of a suitable charset is unnecessary). But 
this means that using the default encoding of the OS won't work. AFAICS the only solution will 
be to add the charset selection box to the Attach File dialog. Then the user will have to select 
the correct charset manually. 
 
As you can see it's not really a bug in KMail. It's simply the result of the lack of a charset entry 
in the vCard. Therefore I changed subject and severity of this bug report.
[prev in list] [next in list] [prev in thread] [next in thread]