Summary: | Composer does not handle unknown characters with incorrect encoding correctly | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Hauke Laging <hauke> |
Component: | composer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | kollix, lemma |
Priority: | NOR | Keywords: | triaged |
Version: | 1.9.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
one of the emails which trigger the buggy behaviour
screenshot |
Description
Hauke Laging
2007-07-11 19:14:01 UTC
Could you please attach such a mail here? Make sure you remove personal things from it first. Created attachment 21157 [details]
one of the emails which trigger the buggy behaviour
The requested file.
Created attachment 21158 [details]
screenshot
This screen shot shows the cursor position after positioning it logically at
the end of the line.
Sure. I have just removed email addresses. I have modified the file with kate. In kate the problematic charachters look different. There is a space and the next character is deleted. I hope kate has not changed anything to these characters. I have not checked that with a hex editor. I also attach a screen shot of the reply window. Please note the cursor position. It is positioned at the ("logical") end of the line. Pressing backspace five times erases everything up to (including) the "t". The cursor is displayed two chars before the end of line. In that case it is displayed between the next "t" and the left rectangle. Pressing backspace again erases the right rectangle but does not move he cursor, reducing the difference between "logical" and "physical" end of line to one character. Hmm, with your mail I can not reproduce the problem. There are strange characters shown, but they don't cause the problems you describe. Maybe editing the file with Kate messed things up indeed. You can check that yourself by downloading your email from this bug report again and saving it somewhere under $HOME/.kde/share/apps/kmail/mail/[..]/cur It should then show up under KMail in that folder. Try replying and see if the problem is still there. If not, then the problem went away after editing the file with Kate. If the problem still occurs with the mail attached here, you should try upgrading KMail to the lastest version. I can't reproduce on trunk r948809 either. I'm unsure if the encoding got messed up, after all I still see some gibberish characters. let's close it then |