After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 85050 - bad charset conversion on followup
bad charset conversion on followup
Status: RESOLVED DUPLICATE of bug 85502
Product: Pan
Classification: Other
Component: general
pre-0.12.0 betas
Other Linux
: Normal normal
: 0.12.1
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-06-12 17:17 UTC by Martin Tomasek
Modified: 2006-06-18 05:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
this is iso-latin-2 signature (92 bytes, application/octet-stream)
2002-07-02 05:13 UTC, Martin Tomasek 		Details
iso-latin-2 attachment (10 bytes, application/octet-stream)
2002-07-02 05:19 UTC, Martin Tomasek 		Details

Description Martin Tomasek 2002-06-12 17:17:31 UTC 
I have:
1. article, which is in iso-8859-2. I should read it correctly.
2. when sending article (in iso-8859-2) all seems to be ok.
3. when I try to reply to 1, characters transferred to 2 are probably in
utf-8, which of course is not displayed correctly in iso-8859-2 article.

hope this is last bug I found today ;-)
Comment 1 Charles Kerr 2002-06-12 17:50:56 UTC 
Actually, it's quite nice to have someone giving the charset
support a heavy workout... keep up the good work!
Comment 2 Christophe Lambin 2002-06-21 23:28:02 UTC 
Martin, could you try explaining this one to me again ?  I can't work
out quite what the problem is.
Comment 3 Martin Tomasek 2002-07-01 11:48:33 UTC 
It seems to me that it disappeared when I updated libraries and
switched to 0.12.
Comment 4 Christophe Lambin 2002-07-01 19:13:38 UTC 
Good to hear, though I suspect the problem is still there: I've found
one issue which could be what you're describing, if I'm in fact
reading your report correctly.

Try setting a signature that contains iso-8859-2 characters and then
create a follow-up to an article that also contains iso-8859-2
characters. Does that reproduce the problem ?
Comment 5 Martin Tomasek 2002-07-01 20:11:36 UTC 
ok, I tried to use iso-latin-2 characters in signature.

with current CVS version:
all is OK, but iso-8859-2 characters in article body are displayed as
"=?iso-8859-2?b?7Lno+L794e3p?=" (and subject in followup as "Re: pokus
-- =?iso-8859-2?b?7Lno+L794e3p?=")

and with 0.12:
signature is ok, but article body seems as utf-8 displayed like
iso-latin-2 ("Δ›ĹĄΔĹ™ĹýåíĂ" instead of "ěčřύανι") and confused editor displays cursor
position one character to right of true cursor. I didn't do testing of
changes in subject field this time.
Comment 6 Christophe Lambin 2002-07-01 20:21:33 UTC 
Many thanks.  As I suspected, this is a duplicate of bug #85502.

For my testing, could you send me a sig with iso-8859-2 characters in
it? They're kinda hard to produce on my qwerty keyboard. :)



*** This bug has been marked as a duplicate of 85502 ***
Comment 7 Martin Tomasek 2002-07-02 05:13:50 UTC 
Created attachment 9575 [details]
this is iso-latin-2 signature
Comment 8 Martin Tomasek 2002-07-02 05:19:38 UTC 
Created attachment 9576 [details]
iso-latin-2 attachment
Comment 9 Martin Tomasek 2002-07-02 05:23:21 UTC 
I added signature in iso-latin-2. Sorry for first file, sigrot was
faster than me and rotated it before I uploaded file.