From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: buffer-swap-text and multibyteness Date: Tue, 10 Feb 2009 20:52:00 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1234266745 8171 80.91.229.12 (10 Feb 2009 11:52:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Feb 2009 11:52:25 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 10 12:53:39 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LWrBJ-0006nQ-0h for ged-emacs-devel@m.gmane.org; Tue, 10 Feb 2009 12:53:37 +0100 Original-Received: from localhost ([127.0.0.1]:59527 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LWr9z-0001Ax-JL for ged-emacs-devel@m.gmane.org; Tue, 10 Feb 2009 06:52:15 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LWr9t-0001Aj-Hs for emacs-devel@gnu.org; Tue, 10 Feb 2009 06:52:09 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LWr9s-0001AX-RG for emacs-devel@gnu.org; Tue, 10 Feb 2009 06:52:09 -0500 Original-Received: from [199.232.76.173] (port=33996 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LWr9s-0001AU-N1 for emacs-devel@gnu.org; Tue, 10 Feb 2009 06:52:08 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:59116) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LWr9o-00059W-G7; Tue, 10 Feb 2009 06:52:05 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id n1ABpxNs017814; Tue, 10 Feb 2009 20:51:59 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id n1ABpwHn019239; Tue, 10 Feb 2009 20:51:58 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id n1ABpwE2024959; Tue, 10 Feb 2009 20:51:58 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.69) (envelope-from ) id 1LWr9k-0006Xu-Ul; Tue, 10 Feb 2009 20:52:00 +0900 In-reply-to: (message from Eli Zaretskii on Tue, 10 Feb 2009 11:12:04 +0200) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:108952 Archived-At: In article , Eli Zaretskii writes: > > > Did you try rmail-redecode-body after editing? > > > > No, but it won't help because when I type C-c C-c after > > editing, the unencodable characters disappear from the > > buffer " *message-viewer RMAIL*". > Do you have an idea why they disappeared? It's because the encoding routine produces a default character for such an unencodable character. Raising an error signal for such a case in the deep place of encoding routine is in my todo list and not yet implemented. > > I got a Japanese mail with attachment file containing many > > non-Japanese characters encoded by emacs-mule. I editted > > the mail, decoded the attached file by hand by the > > combination of base64-decode-region and > > decode-coding-region, and typed C-c C-c. > I do this a lot, but I don't use decode-coding-region. I use > base64-decode-region, then type "C-c C-c" followed by "M-x > rmail-redecode-body RET". This did work for me after the last series > of changes in Rmail. If it doesn't work for you with the current CVS, > can you somehow forward to me the original message, before your > editing, so I could try reproducing what you did? rmail-redecode-body works only when the whole message body is encoded by a single coding system, which is not the case in my scenario above. Please try your method with this mail. Here, I enter Japanese "Hello": こんにちは And, here I enter base64-encoded Latin-1 text: ICAgICBBeCCgIKEgoiCjIKQgpSCmIKcgqCCpIKogqyCsIK0griCvCiAgICAgQnggsCCxILIgsyC0 ILUgtiC3ILgguSC6ILsgvCC9IL4gvwogICAgIEN4IMAgwSDCIMMgxCDFIMYgxyDIIMkgyiDLIMwg zSDOIM8KICAgICBEeCDQINEg0iDTINQg1SDWINcg2CDZINog2yDcIN0g3iDfCiAgICAgRXgg4CDh IOIg4yDkIOUg5iDnIOgg6SDqIOsg7CDtIO4g7wogICAgIEZ4IPAg8SDyIPMg9CD1IPYg9yD4IPkg +iD7IPwg/SD+IP8K And, I send this message itself using charset=iso-2022-jp. --- Kenichi Handa handa@m17n.org