GNU bug report logs - #12362
GNUS can no longer read UTF-8

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 12362 in the body.
You can then email your comments to 12362 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: handa <at> m17n.org
Cc: acid <at> debian.org, bug-gnu-emacs <at> gnu.org, ding <at> gnus.org
Subject: GNUS can no longer read UTF-8
Date: Thu, 06 Sep 2012 05:32:02 +0800

Starting with

emacs-snapshot:
  Installed: 2:20120905-1
  Candidate: 2:20120905-1
  Version table:
 *** 2:20120905-1 0
        500 http://emacs.naquadah.org/ unstable/ Packages
        100 /var/lib/dpkg/status

Even the *Summary* buffers come up garbled.

Try reading even this group,
Newsgroups: gwene.cc.ptt.rss.geography
NNTP-Posting-Host: sea.gmane.org
Content-Type: text/html; charset=utf-8

Message #8 received at 12362 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: jidanni <at> jidanni.org
Cc: acid <at> debian.org, 12362 <at> debbugs.gnu.org, ding <at> gnus.org, handa <at> m17n.org
Subject: Re: bug#12362: GNUS can no longer read UTF-8
Date: Thu, 06 Sep 2012 00:39:06 +0200

jidanni <at> jidanni.org writes:

> Even the *Summary* buffers come up garbled.
>
> Try reading even this group,

Are you sure that the messages are valid?  This is the first subject:

=?utf-8?q?[=e6=96=b0=e8=81=9e]_=e8=bb=8a=e7=ab=99=e6=94=b9=e5=90=8d_=e4=b8=96=e5=8d=9a=e7=ab=99=e2=86=92=e5=8d=83=e7=94=b2=e7=ab=99=e3=80=81=e7=ab=b9=e7=a7=91=e7=ab=99=e2=86=92=e6=96=b0=e8=8e=8a?=

(rfc2047-decode-string
"=?utf-8?q?[=e6=96=b0=e8=81=9e]_=e8=bb=8a=e7=ab=99=e6=94=b9=e5=90=8d_=e4=b8=96=e5=8d=9a=e7=ab=99=e2=86=92=e5=8d=83=e7=94=b2=e7=ab=99=e3=80=81=e7=ab=b9=e7=a7=91=e7=ab=99=e2=86=92=e6=96=b0=e8=8e=8a?=")
=> "[新聾] \350۪\347˙改吭 世孺\347˙→孃甲\347˙、\347˹科\347˙→新讪"

Which contains invalid characters, I think?  Or perhaps not.  I'm not an
expert on ... that.

-- 
(domestic pets only, the antidote for overdose, milk.)
  http://lars.ingebrigtsen.no  *  Lars Magne Ingebrigtsen

Message #11 received at 12362 <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: larsi <at> gnus.org
Cc: acid <at> debian.org, 12362 <at> debbugs.gnu.org, ding <at> gnus.org, handa <at> m17n.org
Subject: Re: bug#12362: GNUS can no longer read UTF-8
Date: Thu, 06 Sep 2012 06:45:44 +0800

The problem happens in ALL groups.
Reverting to
emacs-snapshot:
  Installed: 2:20120829-1
  Candidate: 2:20120905-1
fixes it.

Message #14 received at 12362 <at> debbugs.gnu.org (full text, mbox):

From: Kenichi Handa <handa.kenichi <at> aist.go.jp>
To: jidanni <at> jidanni.org
Cc: acid <at> debian.org, larsi <at> gnus.org, ding <at> gnus.org, 12362 <at> debbugs.gnu.org
Subject: Re: bug#12362: GNUS can no longer read UTF-8
Date: Thu, 06 Sep 2012 11:01:35 +0900

In article <87vcfsf5rb.fsf <at> jidanni.org>, jidanni <at> jidanni.org writes:

> The problem happens in ALL groups.
> Reverting to
> emacs-snapshot:
>   Installed: 2:20120829-1
>   Candidate: 2:20120905-1
> fixes it.

That's because of my recent change to
quoted-printable-decode-region for speed up.  In this code,
I misunderstood the meaning of "(case-fold-search t)", and
handled only "[0-9A-Z]" (no lowercase letters).  RFC2045
also says:

 (1)   (General 8bit representation) Any octet, except a CR or
          LF that is part of a CRLF line break of the canonical
          (standard) form of the data being encoded, may be
          represented by an "=" followed by a two digit
          hexadecimal representation of the octet's value.  The
          digits of the hexadecimal alphabet, for this purpose,
          are "0123456789ABCDEF".  Uppercase letters must be
          used; lowercase letters are not allowed.
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Anyway, I've just installed a fix to handle also 'a'..'f'
(in spite of RFC2045's definition).  Could you please try
again?

---
Kenichi Handa
handa <at> m17n.org

Message #17 received at 12362 <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: handa.kenichi <at> aist.go.jp
Cc: acid <at> debian.org, larsi <at> gnus.org, ding <at> gnus.org, 12362 <at> debbugs.gnu.org
Subject: Re: bug#12362: GNUS can no longer read UTF-8
Date: Thu, 06 Sep 2012 20:46:59 +0800

>>>>> "K" == Kenichi Handa <handa.kenichi <at> aist.go.jp> writes:
K> Could you please try again?
OK I'll try with next week's snapshot.

Also now when I do
$ emacs -f gnus
but not
$ emacs
I get a mysterious new buffer
*Compile-Log*
that contains this mysterious content

Warning: Use `with-current-buffer' rather than save-excursion+set-buffer
Warning: (lambda (x) ...) quoted with ' rather than with #'

With no indication in the world as to what files in the world it is
talking about!!

So I changed

(add-hook
 'gnus-startup-hook
 '(lambda ()

to

(add-hook
 'gnus-startup-hook
 #(lambda ()

like the stupid advice said and... of course fell for the stupid trick
like a dummy. I reverted it.

You can go ahead and check my http://jidanni.org/comp/configuration/

I don't think the warnings are referring to me.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.