From: Dave Love <d.love@liverpool.ac.uk>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: "1770@emacsbugs.donarmstrong.com"
<1770@emacsbugs.donarmstrong.com>,
"emacs-pretest-bug@gnu.org" <emacs-pretest-bug@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 [thread overview]
Message-ID: <878wpmdc9l.fsf@liv.ac.uk> (raw)
In-Reply-To: 87k59d4apn.fsf@marauder.physik.uni-ulm.de
Reiner Steib <reinersteib+gmane@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.
next prev parent reply other threads:[~2009-01-07 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 22:09 bug#1770: 23.0.60; (message-check 'illegible-text ...) fails on eight-bit chars Reiner Steib
2009-01-03 3:23 ` Stefan Monnier
2009-01-07 21:41 ` Dave Love [this message]
[not found] ` <gk38s6$pa7$2@quimby.gnus.org>
2009-01-08 20:28 ` Reiner Steib
2009-01-16 7:45 ` Kenichi Handa
2010-09-30 17:48 ` Lars Magne Ingebrigtsen
2010-10-14 6:37 ` Kenichi Handa
2010-10-14 19:19 ` Lars Magne Ingebrigtsen
2011-01-24 2:55 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878wpmdc9l.fsf@liv.ac.uk \
--to=d.love@liverpool.ac.uk \
--cc=1770@emacsbugs.donarmstrong.com \
--cc=Reiner.Steib@gmx.de \
--cc=emacs-pretest-bug@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.