Parsing of Kai's Emails fails now completlty

Parsing of Kai's Emails fails now completlty

[Andreas Jaeger]

I just did a cvs update an now get the following when trying to
display one of Kai's mails on the ding list:

Signaling: (wrong-type-argument char-or-string-p nil)
  mail-decode-encoded-word-region(1 2458)
  article-decode-encoded-words()
  run-hooks(article-decode-encoded-words)
  gnus-request-article-this-buffer(1420 "nnmaildir+gromit:mail.ding")
  gnus-article-prepare(1420 nil)
  gnus-summary-display-article(1420)
  gnus-summary-next-page(nil)
  call-interactively(gnus-summary-next-page)

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Parsing of Kai's Emails fails now completlty

[Xavier Maillard]

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

On 4 mai 2003, Andreas Jaeger spake thusly:

>  I just did a cvs update an now get the following when trying to
>  display one of Kai's mails on the ding list:
>  
>  Signaling: (wrong-type-argument char-or-string-p nil)
>  mail-decode-encoded-word-region(1 2458)
>  article-decode-encoded-words()
>  run-hooks(article-decode-encoded-words)
>  gnus-request-article-this-buffer(1420 "nnmaildir+gromit:mail.ding")
>  gnus-article-prepare(1420 nil)
>  gnus-summary-display-article(1420)
>  gnus-summary-next-page(nil)
>  call-interactively(gnus-summary-next-page)
>  
>  Andreas

No problem here. Maybe it is related to your settings ?
-- 
http://www.gnusfr.org -- French Gnus user site

Anti-war disclaimer:
	"Bombing for peace is like fucking for virginity"

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

Re: Parsing of Kai's Emails fails now completlty

[Andreas Jaeger]

Xavier Maillard <zedek@gnu-rox.org> writes:

> On 4 mai 2003, Andreas Jaeger spake thusly:
>
>>  I just did a cvs update an now get the following when trying to
>>  display one of Kai's mails on the ding list:
>>  
>>  Signaling: (wrong-type-argument char-or-string-p nil)
>>  mail-decode-encoded-word-region(1 2458)
>>  article-decode-encoded-words()
>>  run-hooks(article-decode-encoded-words)
>>  gnus-request-article-this-buffer(1420 "nnmaildir+gromit:mail.ding")
>>  gnus-article-prepare(1420 nil)
>>  gnus-summary-display-article(1420)
>>  gnus-summary-next-page(nil)
>>  call-interactively(gnus-summary-next-page)
>>  
>>  Andreas
>
> No problem here. Maybe it is related to your settings ?

Might be.  What should I check?  I just did another CVS update and
DAve's change:
        (rfc2047-parse-and-decode): Revert last change.
Fixed the immediate problem.  But Kai's from still looks broken:
From: kai.grossjohann@gmx.net (Kai =?iso-8859-1?q?Gro=DFjohann?=)

Note that:
`mail-decode-encoded-word-region' is an alias for `rfc2047-decode-region', an interactive compiled Lisp function

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Parsing of Kai's Emails fails now completlty

[Christoph Garbers]

* Andreas Jaeger <aj@suse.de>:

> I just did a cvs update an now get the following when trying to
> display one of Kai's mails on the ding list:

No problems here with Kai's mails.

Christoph

Re: Parsing of Kai's Emails fails now completlty

[Xavier Maillard]

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

On 4 mai 2003, Andreas Jaeger uttered the following:

>  Xavier Maillard <zedek@gnu-rox.org> writes:
>
> >  On 4 mai 2003, Andreas Jaeger spake thusly:
> >
> > >  I just did a cvs update an now get the following when trying to
> > >  display one of Kai's mails on the ding list:
> > >
> > >  Signaling: (wrong-type-argument char-or-string-p nil)
> > >  mail-decode-encoded-word-region(1 2458)
> > >  article-decode-encoded-words()
> > >  run-hooks(article-decode-encoded-words)
> > >  gnus-request-article-this-buffer(1420
> > >  "nnmaildir+gromit:mail.ding") gnus-article-prepare(1420 nil)
> > >  gnus-summary-display-article(1420) gnus-summary-next-page(nil)
> > >  call-interactively(gnus-summary-next-page)
> > >
> > >  Andreas
> >
> >  No problem here. Maybe it is related to your settings ?
>
>  Might be.  What should I check?  I just did another CVS update and
>  DAve's change:
>  (rfc2047-parse-and-decode): Revert last change.
>  Fixed the immediate problem.  But Kai's from still looks broken:
>  From: kai.grossjohann@gmx.net (Kai =?iso-8859-1?q?Gro=DFjohann?=)

i definetely don't have this problem here even with a recent cvs up. I
can see the weird symbol without problems. Dunno where you should start
your verifications :( Maybe try to check for the default charset you
are using or stuff like that ?

>  Note that: `mail-decode-encoded-word-region' is an alias for
>  `rfc2047-decode-region', an interactive compiled Lisp function
Yep :

,----[ C-h f mail-decode-encoded-word-region RET ]
| mail-decode-encoded-word-region is an alias for `rfc2047-decode-region' in `mail-parse'.
| (mail-decode-encoded-word-region START END)
|
| Decode MIME-encoded words in region between START and END.
|
| [back]
`----

zeDek
--
http://www.gnusfr.org -- French Gnus user site

Anti-war disclaimer:
	"Bombing for peace is like fucking for virginity"

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

Re: Parsing of Kai's Emails fails now completlty

[Reiner Steib]

On Tue, May 06 2003, Xavier Maillard wrote:

> i definetely don't have this problem here even with a recent cvs up. I
> can see the weird symbol without problems. Dunno where you should start
> your verifications :( Maybe try to check for the default charset you
> are using or stuff like that ?

Maybe you should look at his header. :-) 

Other XEmacs users reported problems with those changes (rfc2047.el,
...), too.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

Re: Parsing of Kai's Emails fails now completlty

[Karl Pflästerer]

On  6 May 2003, Xavier Maillard <- zedek@gnu-rox.org wrote:

> i definetely don't have this problem here even with a recent cvs up. I
> can see the weird symbol without problems. Dunno where you should start
> your verifications :( Maybe try to check for the default charset you
> are using or stuff like that ?

Perhaps it has something to do with Emacs and XEmacs?  I had here the
same problems and because of that switched back to version 5.10.1. No
everything is fine. So there must have been a change in the Gnus code
which broke the char decoding.

It's very bad I can't use a newer Gnus as there are a lot of funny chars
on my screen (can't read utf8, simple iso-8859-1 encoded headers (like
mine) aren't decoded).

bye
   KP

-- 
      And has thou slain the Jabberwock?
          Come to my arms, my beamish boy!
      O frabjous day!  Callooh!  Callay!'
          He chortled in his joy.   "Lewis Carroll" "Jabberwocky"

Re: Parsing of Kai's Emails fails now completlty

[Andreas Jaeger]

[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]

Xavier Maillard <zedek@gnu-rox.org> writes:

> On 4 mai 2003, Andreas Jaeger uttered the following:
>
>>  Xavier Maillard <zedek@gnu-rox.org> writes:
>>
>> >  On 4 mai 2003, Andreas Jaeger spake thusly:
>> >
>> > >  I just did a cvs update an now get the following when trying to
>> > >  display one of Kai's mails on the ding list:
>> > >
>> > >  Signaling: (wrong-type-argument char-or-string-p nil)
>> > >  mail-decode-encoded-word-region(1 2458)
>> > >  article-decode-encoded-words()
>> > >  run-hooks(article-decode-encoded-words)
>> > >  gnus-request-article-this-buffer(1420
>> > >  "nnmaildir+gromit:mail.ding") gnus-article-prepare(1420 nil)
>> > >  gnus-summary-display-article(1420) gnus-summary-next-page(nil)
>> > >  call-interactively(gnus-summary-next-page)
>> > >
>> > >  Andreas
>> >
>> >  No problem here. Maybe it is related to your settings ?
>>
>>  Might be.  What should I check?  I just did another CVS update and
>>  DAve's change:
>>  (rfc2047-parse-and-decode): Revert last change.
>>  Fixed the immediate problem.  But Kai's from still looks broken:
>>  From: kai.grossjohann@gmx.net (Kai =?iso-8859-1?q?Gro=DFjohann?=)
>
> i definetely don't have this problem here even with a recent cvs up. I
> can see the weird symbol without problems. Dunno where you should start
> your verifications :( Maybe try to check for the default charset you
> are using or stuff like that ?

I'm appending the contents of a Gnus bug report.  The important stuff is:
(setq gnus-default-charset
      'iso-8859-1)
(setq message-default-charset
      'iso-8859-1)

Andreas

Gnus v5.10.2
XEmacs 21.4 (patch 12) "Portable Code" [Lucid] (i386-suse-linux, Mule) of Mon Mar 17 2003 on E120
200 gromit.moeb InterNetNews server INN 2.3.4 ready


[-- Attachment #2: User settings --]
[-- Type: application/emacs-lisp, Size: 10941 bytes --]

[-- Attachment #3: Type: text/plain, Size: 100 bytes --]


-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Parsing of Kai's Emails fails now completlty

[Dave Love]

sigurd@12move.de (Karl Pflästerer) writes:

> Perhaps it has something to do with Emacs and XEmacs?

Yes.

> It's very bad I can't use a newer Gnus as there are a lot of funny chars
> on my screen (can't read utf8, simple iso-8859-1 encoded headers (like
> mine) aren't decoded).

As far as I know, all the problems people have found are fixed in
CVS.  It would be helpful to report bugs to the bug address, which I
have been looking at.

Sorry the rfc2047 changes caused trouble for XEmacs.  I thought they
had been tested there when I installed them in Emacs originally, but
obviously not.

Re: Parsing of Kai's Emails fails now completlty

[Karl Pflästerer]

On  9 May 2003, Dave Love <- d.love@dl.ac.uk wrote:

> As far as I know, all the problems people have found are fixed in
> CVS.  It would be helpful to report bugs to the bug address, which I
> have been looking at.

I'll try the CVS head version tommorrow.  Regarding the bug address: I
used all the time the ding list to report bugs (as a lot of other people
too).  It was never said before that this should be wrong.  But I now
subscribed also the gnus bugs ng on gmane.

> Sorry the rfc2047 changes caused trouble for XEmacs.  I thought they
> had been tested there when I installed them in Emacs originally, but
> obviously not.

Well that's the risk of using beta versions. I didn't want to complain
because it's only my risk if I use a beta version but I read the
changelogs and also the postings here and got the feeling that it was
thought everything would be okay.


bye
   KP

-- 
"Programs must be written for people to read, and only incidentally
for machines to execute."
                -- Abelson & Sussman, SICP (preface to the first edition)

Re: Parsing of Kai's Emails fails now completlty

[Andreas Jaeger]

Dave Love <d.love@dl.ac.uk> writes:

> Sorry the rfc2047 changes caused trouble for XEmacs.  I thought they
> had been tested there when I installed them in Emacs originally, but
> obviously not.

Everything seems to be fixed now,

Thanks,
Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Parsing of Kai's Emails fails now completlty

[Karl Pflästerer]

On  9 May 2003, Andreas Jaeger <- aj@suse.de wrote:

> Dave Love <d.love@dl.ac.uk> writes:

>> Sorry the rfc2047 changes caused trouble for XEmacs.  I thought they
>> had been tested there when I installed them in Emacs originally, but
>> obviously not.

> Everything seems to be fixed now,

It seems so.  Very good.  Thanks a lot to the one who found the error.

bye
   KP

-- 
"Programs must be written for people to read, and only incidentally
for machines to execute."
                -- Abelson & Sussman, SICP (preface to the first edition)

Re: Parsing of Kai's Emails fails now completlty

[Dave Love]

sigurd@12move.de (Karl Pflästerer) writes:

> I'll try the CVS head version tommorrow.  Regarding the bug address: I
> used all the time the ding list to report bugs (as a lot of other people
> too).

Maybe I'm confused about its purpose.  If that's what people should
do, I think the bugs address should be redirected here.

> It was never said before that this should be wrong.  But I now
> subscribed also the gnus bugs ng on gmane.

You certainly shouldn't need to subscribe to a bugs list if you report
bugs.  It's a bug if people responding don't copy responses to the
submitter.  (I know they often don't.)

> Well that's the risk of using beta versions. I didn't want to complain
> because it's only my risk if I use a beta version 

Please complain (for useful values of `complain')!  You're right that
there's a risk to using test versions -- and I think people are too
often encouraged to do that -- but if you're willing to, the feedback
should be very welcome.  Thanks.