Summary: | always claiming wrong coding of written text in email | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | gerd <gerd> |
Component: | composer | Assignee: | 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
Could you attach that file? Please use link above and go to the bottom to do that.... 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
Created attachment 7459 [details]
Another example with explicit utf-8 encoding which causes a pop-up warning
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? 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. ********************************************************************** 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? *** Bug 106155 has been marked as a duplicate of this bug. *** 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) *** Bug 175364 has been marked as a duplicate of this bug. *** 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 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 |