unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Reiner.Steib@gmx.de, d.love@liverpool.ac.uk, 1770@debbugs.gnu.org
Subject: bug#1770: 23.0.60; (message-check 'illegible-text ...) fails on eight-bit chars
Date: Thu, 14 Oct 2010 15:37:30 +0900	[thread overview]
Message-ID: <tl7sk09i8k5.fsf@m17n.org> (raw)
In-Reply-To: <m3tyl7gm1v.fsf@quimbies.gnus.org> (message from Lars Magne Ingebrigtsen on Thu, 30 Sep 2010 19:48:12 +0200)

In article <m3tyl7gm1v.fsf@quimbies.gnus.org>, Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Kenichi Handa <handa@m17n.org> writes:
> > Yes.  For Emacs 23, adding eight-bit in the list is ok.
> > But, I think it is better to catch non-Unicode characters
> > (#x110000..#x3FFF7F) here too.  For Emacs 23 only, we can
> > have this simple code:
> >
> > 	(while (not (eobp))
> > 	  (when (not (encode-char (char-after) 'unicode))
> >                 ;; or simply (>= (char-after) #x110000)
> > 	    (if (eq choice ?i)
> > 		(message-kill-all-overlays)
> > 	      (delete-char 1)
> > 	      (when (eq choice ?r)
> > 		(insert message-replacement-char))))
> > 	  (forward-char)
> > 	  (skip-chars-forward mm-7bit-chars))

> Was this installed?

No.

> If not, was a different fix applied, 

Yes.

2009-01-03  Reiner Steib  <Reiner.Steib@gmx.de>

	* message.el (message-fix-before-sending): Add `eight-bit' to
	illegible-text check.

> and the bug not closed, or is this still a problem?

As I wrote, non-Unicode characters are still not caught
here.  But I'm not sure it's problem to be solved by
message-fix-before-sending.  I have not yet got a reply to
this question.

> After filtering out those strange characters, how is a
> coding system decided?  Is select-message-coding-system
> used?

---
Kenichi Handa
handa@m17n.org





  reply	other threads:[~2010-10-14  6:37 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
     [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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tl7sk09i8k5.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=1770@debbugs.gnu.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=d.love@liverpool.ac.uk \
    --cc=larsi@gnus.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).