From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dan Jacobson Newsgroups: gmane.emacs.bugs Subject: mule: why not show the damage of choosing "raw-text" etc. now? Date: 24 Apr 2002 02:07:06 +0800 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: Reply-To: jidanni@yam.com.tw NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1019607503 16208 127.0.0.1 (24 Apr 2002 00:18:23 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 24 Apr 2002 00:18:23 +0000 (UTC) Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 170AUH-0004DJ-00 for ; Wed, 24 Apr 2002 02:18:22 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 170AUG-0005jJ-00; Tue, 23 Apr 2002 20:18:20 -0400 Original-Received: from chx400.switch.ch ([130.59.10.2]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 170ASg-0005bp-00 for ; Tue, 23 Apr 2002 20:16:43 -0400 Original-Received: from mail.fu-berlin.de ([160.45.11.165]) by chx400.switch.ch with esmtp (Exim 3.20 #1) id 170ASe-0007Mk-00 for gnu-emacs-bug@moderators.isc.org; Wed, 24 Apr 2002 02:16:40 +0200 Original-Received: by mail.fu-berlin.de (Smail3.2.0.98) from Curry.ZEDAT.FU-Berlin.DE (160.45.10.36) with esmtp id ; Wed, 24 Apr 2002 02:16:38 +0200 (MEST) Original-Received: by Curry.ZEDAT.FU-Berlin.DE (Smail3.2.0.98) from news.fu-berlin.de with bsmtp id ; Wed, 24 Apr 2002 02:16:37 +0200 (MEST) Original-To: gnu-emacs-bug@moderators.isc.org Original-Path: 61-227-44-234.hinet-ip.hinet.NET!not-for-mail Original-Newsgroups: gnu.emacs.bug Original-Lines: 31 X-Orig-NNTP-Posting-Host: 61-227-44-234.hinet-ip.hinet.net (61.227.44.234) X-Orig-X-Trace: fu-berlin.de 1019607396 7722821 61.227.44.234 (16 [99749]) X-Orig-Path: localhost.localdomain!nobody User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:897 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:897 I do a certain M-x compile command that produces output that looks like normal big5 chinese... at least the first page of which that I see in the split window. I attempt to write this to disk with C-x C-w some_filename. Due to some non-big5 character somewhere deep in the output, I encounter These default coding systems were tried: chinese-big5-unix However, none of them safely encodes the target text. Select one of the following safe coding systems: raw-text emacs-mule no-conversion Well, whichever choice I make **_the file still looks good on my screen_**, until of course the next time I start emacs (or the less pager), when it has then become a unrecoverable bunch of <98>'s. My point is, _why allow the file to keep on looking good this session?_ If you are going to turn it into a "unrecoverable bunch of <98>'s", why not do it now in front of the user's face instead of having him think that the file is A-OK, and can be e-mailed to friends, or is ready to go for the big presentation tomorrow? Sure, emacs has its reasons for being unable to save the file in the character set I wanted. OK, fine. But why keep on displaying the file in the comfortable character set instead of tipping of the user of what the file now looks like next time he attempts to read it? -- http://jidanni.org/ Taiwan(04)25854780