Bug 88781

Summary: always claiming wrong coding of written text in email
Product: [Unmaintained] kmail Reporter: gerd <gerd>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: jtamate, paje, rusty
Priority: NOR Keywords: triaged
Version: 1.6.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Its a signature which I am using very often
Another example with explicit utf-8 encoding which causes a pop-up warning

Description gerd 2004-09-03 17:46:24 UTC
Version:           1.6.2 (using KDE 3.2.1, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.4-52-default

When I am inserting a plain text from a file into the email text by the file-meue-option insert file then a popup-menue appears claiming that no approriate code is available. But in the options for the editor is 'pre-wired' : 
us-ascii
iso-8859-1
utf-8(locale)
utf-8
When I am sending the text without having the right encoding and when i afterwards copy the received text into my email, then no warnings appear. 
If I --instead of insertig the problem-text by the file option-- am doing copy-and-paste then no warnings appears.
Perhaps this is simple.
I don't see it at the moment.

best regards

gerd

The text which is causing the problem is here:

Email: doeben@fb2.fh-frankfurt.de
Email: gerd_doeben-henisch@ieee.org
URL:http://www.fbmnd.fh-frankfurt.de/~doeben

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************

Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen.  Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
irrtuemlich
erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie 
diese
E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail 
ist
nicht gestattet. 
**********************************************************************
Comment 1 Tom Albers 2004-09-08 17:39:04 UTC
Could you attach that file? Please use link above and go to the bottom to do that....
Comment 2 gerd 2004-09-08 20:25:17 UTC
Created attachment 7458 [details]
Its a signature which I am using very often

I have	created an additional textfile with explicit utf-8 encoding. Inserting
this through the file menue yields the same pop-menue with warnings.  Thus it
seems that the insertion-mechanism has problems with the encodings (or the
program in recognizing ...).

gerd d-h
Comment 3 gerd 2004-09-08 20:28:41 UTC
Created attachment 7459 [details]
Another example with explicit utf-8 encoding which causes a pop-up warning
Comment 4 Tom Albers 2004-09-09 19:10:57 UTC
In the insert file dialog there is a pulldown where you can select the encoding. Whatever I select I don't get a warning, but only with utf-8  it is readable.  The rest is if your report is a bit difficult to follow, could you explain somewhat clearer?
Comment 5 gerd 2004-09-09 19:39:30 UTC
Hi Tom,

meanwhile I have probably found a first hint:

everytime when I am inserting a textfile with the file-option (and the setting 
unicode utf-8 in the option right up in the window) then there is some 
strange sign AT THE END OF THE TEXT. When I am explicitly delete this 
additional strange sign then no warnings appear any more and everything works 
fine.

This is fine because I am overall quite lucky with kontact; I have been 
migrated  from evolution to kontact because evolution had in the new version 
a severe bug. 

because I will leave saturday or 3 weeks  can continue the discussion to this 
bug only after oct-3.

Thanks for your assistance and best regards

gerd d-h

PS: I have left this strange sign now intentiously at the end of this email; I 
am not sure whether it will survice the processing of the message...

Am Donnerstag, 9. September 2004 19:10 schrieb Tom Albers:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=88781
>
>
>
>
> ------- Additional Comments From tomalbers kde nl  2004-09-09 19:10 -------
> In the insert file dialog there is a pulldown where you can select the
> encoding. Whatever I select I don't get a warning, but only with utf-8  it
> is readable.  The rest is if your report is a bit difficult to follow,
> could you explain somewhat clearer?

--------------------------------------------------------------------

FACHHOCHSCHULE FRANKFURT - FB2 Informatik u. Ingenieurwissenschaften
UNIVERSITY  of APPLIED SCIENCES FRANKFURT - FB2 Computer Science & Engineering

Prof. Dr. Gerd Doeben-Henisch

Tel-Office: ++49-69-1533-3014 
Tel-Priv. 0049-(0)700-437 336 32 (= 0049-(0)700-gerddoeb)
Email: doeben@fb2.fh-frankfurt.de
Email: gerd_doeben-henisch@ieee.org
Email: gerd@doeben-henisch.de
URL:http://www.fbmnd.fh-frankfurt.de/~doeben

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************

Comment 6 A T Somers 2006-10-29 11:43:00 UTC
If I try to insert a file now (KDE 3.5.5), I don't get a dialog at all. You just select the file, and it works. However, I do get a couple of strange signs at the start of the text, so I think something is still not well here. Could you please verify with a recent KDE?
Comment 7 Thomas McGuire 2007-05-08 15:43:43 UTC
*** Bug 106155 has been marked as a duplicate of this bug. ***
Comment 8 Jaime Torres 2008-09-10 18:06:48 UTC
Stll present, with the strange character at the end of the inserted text (even inserting an empty file) in kmail 1.10.1 (svn trunk 857915)
Comment 9 Jaime Torres 2008-11-17 10:24:12 UTC
*** Bug 175364 has been marked as a duplicate of this bug. ***
Comment 10 Thomas McGuire 2008-11-18 20:54:39 UTC
SVN commit 886205 by tmcguire:

When inserting a file to the composer:

- Don't add a zero-terminator to the end
- Check if the content can still be encoded with the current charset.
  If not, change the mode to auto-charset detection.

BUG: 88781



 M  +47 -19    kmcomposewin.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=886205
Comment 11 Thomas McGuire 2008-11-30 16:36:32 UTC
SVN commit 890879 by tmcguire:

Backport r886205 by tmcguire from trunk to the 4.1 branch:

When inserting a file to the composer:

- Don't add a zero-terminator to the end
- Check if the content can still be encoded with the current charset.
  If not, change the mode to auto-charset detection.

CCBUG: 88781




 M  +50 -19    kmcomposewin.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=890879