I believe this was fixed upstream. Can you please confirm?
** Changed in: gnubiff (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: gnubiff (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0lf)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I merged the patch from CVS to my 2.2.10 branch. It works fine here...
Maybe you want to test the patch (click raw to download):
http://freehg.org/u/misery/gnubiff/rev/a956b3d06ac1
--
Can't convert us-ascii to UTF8
https://bugs.launchpad.net/bugs/161831
You received this bug notification
Comment from author on sf.net:
Date: 2008-04-19 16:21
Sender: sowadart
Obviously this is not a bug in gnubiff but a bug in the application that
creates the message in a wrong character set.
BTW: In the development CVS version 2.3.0 there is an option
popup_convert_strip_non_ascii (by default
I did a couple of tests myself. It seems that the error message is just badly
chosen - the problem is not that gnubiff cannot convert us-ascii to UTF-8 but
that the conversion fails because the original message isn't in the charset it
claims to be (in that case us-ascii).
Here are the
I forwarded this bug to upstream.
** Bug watch added: SourceForge.net Tracker #1924450
http://sourceforge.net/support/tracker.php?aid=1924450
** Also affects: gnubiff via
http://sourceforge.net/support/tracker.php?aid=1924450
Importance: Unknown
Status: Unknown
--
Can't convert
Do you have a mail for this?
I looked into it with a mail that have this problem. The problem is that this
mail has no content type: ... charset: -header.
And if you see in source mailbox.cc:726 you will see that mails like this will
be us-ascii by default (RFC 2045) but this mail isn't
Confirmed. I have that problem, too.
** Changed in: gnubiff (Ubuntu)
Status: New = Confirmed
--
Can't convert us-ascii to UTF8
https://bugs.launchpad.net/bugs/161831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
