Bug#483246: iceweasel: fails to show/send/save data because of a bad char.
Hello, your bug is quite a little bit older. I think your described errors may be gone thruy the last versions from icedove. Can you give a feedback of your actual status? This problems are still exist? Or may the bug be closed? Regards Carsten On Wed, May 28, 2008 at 01:28:00AM +0300, db...@sanevision.com wrote: Package: iceweasel Version: 2.0.0.12-1 Severity: important The important bug is given by the subject, but there are several less troublesome satellite bugs here. Here's the full story. I had an email message that contained some bad characters. I was trying to reply to it. The message claimed to be of ISO-8859-1 encoding, but it contained the UTF-8 char 0xc481 (and many others, but this was the one causing the main problem). Getting rid of all occurences of this char let me send the message, but this was an unacceptably tedious and needless procedure, IMHO. Here's the list of things I consider bugs: 1) Any characters following the 0xc481 (Ä) weren't shown. Not sure how many weren't and after which char they began showing but quite a bunch were invisible. I don't mean that they were garbled, that I'd expect to be the normal behavior; they were plain invisible. Underlined for being misspelled, though. :-) 2) Saving the msg as a draft saved it only until the 0xc481 char (don't remember inclusive or not). The rest of the text was lost w/o any warning. 3) Sending the reply stalled in the Sending msg. dialog, until finally Iceweasel gave up, closed the TCP connection and announced: Sending of message failed. The message could not be sent because connecting to SMTP server blah.blah.blah failed. The server may be unavailable or is refusing SMTP connections. Please verify that your SMTP server setting is correct and try again, or else contact your network administrator. 4) This was, obviously, incorrect and misleading, as the server was fine, it had been connected just fine, and data had been sent up to the 0xc481 char (not inclusively), and then there had been some more bytes sent (which seemed to change a bit from try to try, but c3 84 2e 0d 0a was one of the things I observed several times). 5) Iceweasel used to have encoding preferences that a normal person could find---apply this encoding by default to incoming msgs, apply this to outgoing, override the original, etc., etc. Now I can't seem to find them. If these preferences are now under the huge list that is supposed to be tweaked with the config editor, well, they can't be found w/o knowing what to look for. I.e., a description or help column would actually make this thing usable. If this has to be done with the Folder Properties---isn't it crazy, setting up your preferred encoding separately for each one? I presume it's not the case. 6) View-Character_Encoding-UTF-8 doesn't help on this msg., probably because it specifies iso-9959-1. Or perhaps because the text is all within a mime-attachement, again with iso-8859-1 promised. Anyway, there seems to be lacking a way to turn all the displayable text to a different encoding, regardless of what the message or its attachements claim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#483246: iceweasel: fails to show/send/save data because of a bad char.
Package: iceweasel Version: 2.0.0.12-1 Severity: important The important bug is given by the subject, but there are several less troublesome satellite bugs here. Here's the full story. I had an email message that contained some bad characters. I was trying to reply to it. The message claimed to be of ISO-8859-1 encoding, but it contained the UTF-8 char 0xc481 (and many others, but this was the one causing the main problem). Getting rid of all occurences of this char let me send the message, but this was an unacceptably tedious and needless procedure, IMHO. Here's the list of things I consider bugs: 1) Any characters following the 0xc481 (Ä) weren't shown. Not sure how many weren't and after which char they began showing but quite a bunch were invisible. I don't mean that they were garbled, that I'd expect to be the normal behavior; they were plain invisible. Underlined for being misspelled, though. :-) 2) Saving the msg as a draft saved it only until the 0xc481 char (don't remember inclusive or not). The rest of the text was lost w/o any warning. 3) Sending the reply stalled in the Sending msg. dialog, until finally Iceweasel gave up, closed the TCP connection and announced: Sending of message failed. The message could not be sent because connecting to SMTP server blah.blah.blah failed. The server may be unavailable or is refusing SMTP connections. Please verify that your SMTP server setting is correct and try again, or else contact your network administrator. 4) This was, obviously, incorrect and misleading, as the server was fine, it had been connected just fine, and data had been sent up to the 0xc481 char (not inclusively), and then there had been some more bytes sent (which seemed to change a bit from try to try, but c3 84 2e 0d 0a was one of the things I observed several times). 5) Iceweasel used to have encoding preferences that a normal person could find---apply this encoding by default to incoming msgs, apply this to outgoing, override the original, etc., etc. Now I can't seem to find them. If these preferences are now under the huge list that is supposed to be tweaked with the config editor, well, they can't be found w/o knowing what to look for. I.e., a description or help column would actually make this thing usable. If this has to be done with the Folder Properties---isn't it crazy, setting up your preferred encoding separately for each one? I presume it's not the case. 6) View-Character_Encoding-UTF-8 doesn't help on this msg., probably because it specifies iso-9959-1. Or perhaps because the text is all within a mime-attachement, again with iso-8859-1 promised. Anyway, there seems to be lacking a way to turn all the displayable text to a different encoding, regardless of what the message or its attachements claim. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24.2 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=lv_LV.UTF-8, LC_CTYPE=lv_LV.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iceweasel depends on: ii debianutils2.28.4Miscellaneous utilities specific t ii fontconfig 2.5.0-2 generic font configuration library ii libatk1.0-01.20.0-1 The ATK accessibility toolkit ii libc6 2.7-6 GNU C Library: Shared libraries ii libcairo2 1.4.14-1 The Cairo 2D vector graphics libra ii libfontconfig1 2.5.0-2 generic font configuration library ii libfreetype6 2.3.5-1+b1FreeType 2 font engine, shared lib ii libgcc11:4.3.0-1 GCC support library pn libglib2.0-0 none(no description available) pn libgtk2.0-0none(no description available) ii libhunspell-1.1-0 1.1.9-1 spell checker and morphological an ii libjpeg62 6b-14 The Independent JPEG Group's JPEG pn libnspr4-0dnone(no description available) pn libnss3-1d none(no description available) pn libpango1.0-0 none(no description available) ii libpng12-0 1.2.15~beta5-3PNG library - runtime ii libstdc++6 4.3.0-1 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxft22.1.12-2 FreeType-based font drawing librar pn libxinerama1 none(no description available) ii libxp6 1:1.0.0.xsf1-1X Printing Extension (Xprint) clie ii libxrender11:0.9.4-1 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii procps 1:3.2.7-6 /proc file system utilities ii psmisc 22.6-1Utilities that use the proc filesy
Bug#483246: iceweasel: fails to show/send/save data because of a bad char.
On Wed, May 28, 2008 at 01:28:00AM +0300, [EMAIL PROTECTED] wrote: Package: iceweasel Version: 2.0.0.12-1 Severity: important The important bug is given by the subject, but there are several less troublesome satellite bugs here. Here's the full story. I had an email message that contained some bad characters. I was trying to reply to it. The message claimed to be of ISO-8859-1 encoding, but it contained the UTF-8 char 0xc481 (and many others, but this was the one causing the main problem). Getting rid of all occurences of this char let me send the message, but this was an unacceptably tedious and needless procedure, IMHO. Here's the list of things I consider bugs: Since when iceweasel is an email client ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483246: iceweasel: fails to show/send/save data because of a bad char.
Sorry, I meant icedove. Can you refile or should I resubmit correctly? Martins 2008/5/28 Mike Hommey [EMAIL PROTECTED]: On Wed, May 28, 2008 at 01:28:00AM +0300, [EMAIL PROTECTED] wrote: Package: iceweasel Version: 2.0.0.12-1 Severity: important The important bug is given by the subject, but there are several less troublesome satellite bugs here. Here's the full story. I had an email message that contained some bad characters. I was trying to reply to it. The message claimed to be of ISO-8859-1 encoding, but it contained the UTF-8 char 0xc481 (and many others, but this was the one causing the main problem). Getting rid of all occurences of this char let me send the message, but this was an unacceptably tedious and needless procedure, IMHO. Here's the list of things I consider bugs: Since when iceweasel is an email client ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483246: iceweasel: fails to show/send/save data because of a bad char.
reassign 483246 icedove thanks On Wed, May 28, 2008 at 08:25:36AM +0300, Martins Krikis wrote: Sorry, I meant icedove. Can you refile or should I resubmit correctly? Martins 2008/5/28 Mike Hommey [EMAIL PROTECTED]: On Wed, May 28, 2008 at 01:28:00AM +0300, [EMAIL PROTECTED] wrote: Package: iceweasel Version: 2.0.0.12-1 Severity: important The important bug is given by the subject, but there are several less troublesome satellite bugs here. Here's the full story. I had an email message that contained some bad characters. I was trying to reply to it. The message claimed to be of ISO-8859-1 encoding, but it contained the UTF-8 char 0xc481 (and many others, but this was the one causing the main problem). Getting rid of all occurences of this char let me send the message, but this was an unacceptably tedious and needless procedure, IMHO. Here's the list of things I consider bugs: Since when iceweasel is an email client ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
