GNOME Bugzilla – Bug 85502
Umlauts (הצ�) / High Bit chars in forwarded/follow-upd articles are "utf-8"
Last modified: 2006-06-18 05:15:43 UTC
When forwarding or follow-up'ing/replying to an article containing Umlauts/high-bit characters like δφό€ (Euro), the letter is "destroyed". Instead of δ, I see Γ€. This looks like Pan stores the articles in UTF-8 internally but doesn't convert that to "plain" letters when composing the new message. This is with the Mandrake RPM pan-0.11.94-2mdk on Mandrake Linux Cooker.
Forgot to set Severity to Major. This is major, because it destroys the articles.
I don't think I can fix this for 0.12.0 without breaking the string freeze. Marking for 0.12.1.
Created attachment 9267 [details] screenshot ot followup
I've just added an attachment of what I see when I hit followup to your test post. The characters look correct to me, am I doing the wrong thing and not tickling the bug? (Side note: I had to change my monospace font because the versions of courier and courier new shipping with RH7.3 don't seem to have the euro symbol...?)
Hmm, strange. With my PC at work, I also cannot reproduce this bug. Here I'm using 0.11.93 - however at home I also had it with 0.11.93. However, at home I can reproduce it. Which packages/settings might influence this?
Alexander: are you still seeing this in 0.12.0 ?
No, I'm not seeing it anymore.
Reopening bug. I noticed that the described behaviour happens, when I use a signature file (see attachment). Without a/this signature, umlauts are preserved just fine. But as soon as I set a .sig in the profiles setting, they are destroyed.
Forgot to say - this happens with 0.12.0
Created attachment 9525 [details] My signature file
Sorry, for all those comments right now... On my PC, the signature file is in iso-8859-1 encoding. When I change the encoding to utf8 using recode, high bit chars are preserved. However, pan should detect if the sig is/might be a UTF8 text, and if it is not, it should convert it first. I don't know how you might detect this, but "file" is able to do so.
Aha! That explains a lot. I'll have this fixed for 0.12.1 / 0.13.0 (whichever comes first). Thanks for tracking this.
*** Bug 85050 has been marked as a duplicate of this bug. ***
Fixed for 0.12.1.