On August 25, 2005 at 7:34PM +0900,
tats (at vega.ocn.ne.jp) wrote:
> To fix this bug, Nedko Arnaudov revised the patch, and I sorted out
> and revised it.
>
> I can now recommend the attached patch.
>
> * feedparser.py (_sync_author_detail): Replace '<>' with ''.
> * rss2email.py (header7bit): Us
reopen 320185
tags 320185 + patch
thanks
On August 20, 2005 at 1:22PM +0900,
tats (at vega.ocn.ne.jp) wrote:
> > > I actually encountered raw non-ASCII bytes in From field.
> > http://nedko.arnaudov.name/soft/rss2email-2.55-folding.patch
> >
> > This patch uses email/Header.py instead of mimif
On August 18, 2005 at 9:24PM +0900,
tats (at vega.ocn.ne.jp) wrote:
> > I actually encountered raw non-ASCII bytes in From field.
>
> I google'd "rss2email mimify", then I found a solution of this
> problem.
>
> Please consider applying the following patch instead of my patch.
>
> http://nedko.a
Hi Joey,
On July 29, 2005 at 6:02AM +0900,
tats (at vega.ocn.ne.jp) wrote:
> I actually encountered raw non-ASCII bytes in From field.
I google'd "rss2email mimify", then I found a solution of this
problem.
Please consider applying the following patch instead of my patch.
http://nedko.arnaud
On July 28, 2005 at 10:36PM +0900,
tats (at vega.ocn.ne.jp) wrote:
> I also found the problem in From field with rss2email. Even if " "
> is added, the value of the follow code contains non-ASCII raw character.
>
> print mimify.mime_encode_header("\"012á34 56789\" ")
Oops, I had a misunderstand
On July 28, 2005 at 6:54PM +0900,
tats (at vega.ocn.ne.jp) wrote:
> > print
> > mimify.mime_encode_header("á12345678901234567890123456789012345678901234567890123456789012345678901234567890")
>
> To reproduce the problem, add " ", " foobar" or so to the string,
> as follows:
>
> print
> mimify.
On July 28, 2005 at 9:46AM -0400,
joeyh (at debian.org) wrote:
> Hmm, still not working:
>
> [EMAIL PROTECTED]:~>python foo
> =?ISO-8859-1?Q?=E11234567890123456789012345678901234567890123456789012?=
> 3456789012345678901234567890 foobar
>
> Can you attach a test case?
Hmm, I tried the fol
Tatsuya Kinoshita wrote:
> To reproduce the problem, add " ", " foobar" or so to the string,
> as follows:
>
> print
> mimify.mime_encode_header("á12345678901234567890123456789012345678901234567890123456789012345678901234567890
> ")
Hmm, still not working:
[EMAIL PROTECTED]:~>python foo
=
On July 27, 2005 at 11:07PM -0400,
joeyh (at debian.org) wrote:
> I'd like to pass this bug on to python besides working around it, but I
> can't seem to reproduce it with a simple test case like this:
>
> #!/usr/bin/python
> # -*- coding: utf-8 -*-
> import mimify
> print
> mimify.mime_encode_h
Tatsuya Kinoshita wrote:
> Package: rss2email
> Version: 1:2.54-6
> Severity: normal
>
> I've tried using rss2email and found a bug.
>
> A Subject field is encoded incorrectly if the RSS feed contains
> non-ASCII characters in the title and the word is too long.
>
> For instance,
>
> á123456789
Tatsuya Kinoshita wrote:
> I've tried using rss2email and found a bug.
>
> A Subject field is encoded incorrectly if the RSS feed contains
> non-ASCII characters in the title and the word is too long.
>
> For instance,
>
> á123456789012345678901234567890123456789012345678901234567890123456789012
Package: rss2email
Version: 1:2.54-6
Severity: normal
I've tried using rss2email and found a bug.
A Subject field is encoded incorrectly if the RSS feed contains
non-ASCII characters in the title and the word is too long.
For instance,
á1234567890123456789012345678901234567890123456789012345678
12 matches
Mail list logo
