GNU bug report logs - #1770
23.0.60; (message-check 'illegible-text ...) fails on eight-bit chars

Previous Next

Packages: gnus, emacs;

Reported by: Reiner Steib <Reiner.Steib <at> gmx.de>

Date: Fri, 2 Jan 2009 22:20:03 UTC

Severity: normal

Found in version 23.0.60

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Dave Love <d.love <at> liverpool.ac.uk>
To: Reiner Steib <Reiner.Steib <at> gmx.de>
Cc: "1770\@debbugs.gnu.org" <1770 <at> debbugs.gnu.org>,
        "emacs-pretest-bug\@gnu.org" <emacs-pretest-bug <at> gnu.org>
Subject: bug#1770: 23.0.60; (message-check 'illegible-text ...) fails on eight-bit chars
Date: Wed, 07 Jan 2009 21:41:58 +0000
Reiner Steib <reinersteib+gmane <at> imap.cc> writes:

> In Emacs 23, (char-charset char) returns `eight-bit'.  Is adding
> eight-bit next to eight-bit-graphic sufficient?  The comment (by Dave
> Love, CC-ed if I got X-Debbugs-CC right) seems to suggest that there's
> more to be done.

You should ask handa about that and other Mule issues.  Experience shows
it's not helpful for me to explain.

There were various things like that I left unfixed for Mule 6 (for
various reasons) five years ago, or whenever it was.

By the way, `undecable' should be `undecodable' in the comment, which
may only apply in Emacs 21 -- I don't know.

I think there are various things wrong with
`message-fix-before-sending'.  The one I remember is it objecting to
stuff in non-text inline MIME parts, e.g. if you try to use
application/octet-stream for a Lisp backtrace.





This bug report was last modified 14 years and 117 days ago.

Previous Next


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