jidanni@jidanni.org wrote:
> My entire
>  g runs the command gnus-group-get-new-news
> run was halted midway upon reaching
> http://radioscanningtw.wikia.com/index.php?title=%E7%89%B9%E6%AE%8A:%E6%9C%80%E8%BF%91%E6%9B%B4%E6%94%B9&feed=rss
> nnrss: Requesting WIKIA Taiwan Radio Scanning Wiki  - 近期變動 [zh-tw]...
> rfc2047-encode: Can't rfc2047-encode `使用者:Ɩ\271富裕'

> Why should one little error bring the entire gnus-group-get-new-news run
> to a halt?

> nnrss-version "nnrss 1.0"

That can happen when not only running `gnus-group-get-new-news'
in a nnrss group if there are funny characters in text to be MIME
encoded.  `rfc2047-encode' uses `mm-find-mime-charset-region' to
determine charset that is used to encode text, and expects that
it returns a list of single valid charset.  However, as the case
may be, it may return a list containing an invalid charset
(actually `nil') or just a list containing a single `nil'.

(with-temp-buffer
  (insert "使用者:Ɩ\271富裕")
  (mm-find-mime-charset-region (point-min) (point-max)))
 => (nil iso-2022-jp)

(The result will vary according to the language environment.)

In the most case it returns `utf-8' nowadays, but the `nil'
element in the result means there is a character that cannot be
encoded by any charset.  For such a case, I've modified
`rfc2047-encode' so as to use `utf-8' as a last resort (the diff
follows).  It is no more than a workaround, i.e. some characters
may be encoded irreversibly, but cannot help it.