From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: decode-coding-string gone awry? Date: Mon, 14 Feb 2005 22:26:52 +0100 Message-ID: References: <874qgf1dkv.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1108417246 31536 80.91.229.2 (14 Feb 2005 21:40:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 14 Feb 2005 21:40:46 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 14 22:40:45 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D0nxN-0004GP-7g for ged-emacs-devel@m.gmane.org; Mon, 14 Feb 2005 22:40:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0oCz-0004P7-7w for ged-emacs-devel@m.gmane.org; Mon, 14 Feb 2005 16:56:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D0oBz-0004DA-L6 for emacs-devel@gnu.org; Mon, 14 Feb 2005 16:55:44 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D0oBp-0004AC-71 for emacs-devel@gnu.org; Mon, 14 Feb 2005 16:55:34 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0oBo-00045V-N2 for emacs-devel@gnu.org; Mon, 14 Feb 2005 16:55:33 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D0nk4-0005GU-3j for emacs-devel@gnu.org; Mon, 14 Feb 2005 16:26:52 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1D0ng1-00078w-UT; Mon, 14 Feb 2005 16:22:42 -0500 Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "Mon, 14 Feb 2005 15:56:17 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33428 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33428 Stefan Monnier writes: >> So that is basically the background why we can easily make the process >> raw-text, but quite less easily make the buffer unibyte: AUCTeX will >> use the same buffer for its next run, just erasing it, and if it has >> turned unibyte, we get into trouble. > > OK. raw-text is good. Just to follow up on my last mail: the raw-text inserted 8bit-characters _are_ displayed with octal escape sequences, just like I wished they were. While I am pretty sure that I _have_ seen something else as well, it would appear that I confused this with what an AUCTeX run (probably with an intentionally wrong process encoding of latin-1) produced, or some earlier iteration of the software. Thanks for all the hand-holding. All this is a bit crazy: first the process "converting" to raw-text, then I taking this, "encoding" raw-text, interpreting the escapes, and decoding to utf-8 or whatever else... But that's a secondary issue. We can try making something more sensible once we have the merger behind us. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum