From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ken Manheimer" Newsgroups: gmane.emacs.devel Subject: interesting encryption/encoding allout problem Date: Sat, 11 Nov 2006 00:35:38 -0500 Message-ID: <2cd46e7f0611102135o17cc805ei8e863ab26dd60013@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1163223361 14078 80.91.229.2 (11 Nov 2006 05:36:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 11 Nov 2006 05:36:01 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 11 06:35:59 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GilWz-0001tm-LH for ged-emacs-devel@m.gmane.org; Sat, 11 Nov 2006 06:35:54 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GilWy-0000CV-PL for ged-emacs-devel@m.gmane.org; Sat, 11 Nov 2006 00:35:52 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GilWn-0000CP-TK for emacs-devel@gnu.org; Sat, 11 Nov 2006 00:35:41 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GilWn-0000CD-Dn for emacs-devel@gnu.org; Sat, 11 Nov 2006 00:35:41 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GilWn-0000CA-9Z for emacs-devel@gnu.org; Sat, 11 Nov 2006 00:35:41 -0500 Original-Received: from [64.233.182.186] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GilWn-000433-5q for emacs-devel@gnu.org; Sat, 11 Nov 2006 00:35:41 -0500 Original-Received: by nf-out-0910.google.com with SMTP id d4so1499417nfe for ; Fri, 10 Nov 2006 21:35:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=cFqOqZgJ4NaxnI9K+d3VZgLXlf2VQaQTWeS5jfOi6an8B4Sp9GCJOx9Od71NWIdkEsbvkW3gTGwCYVmsWmjmKIUDyFlxMAf1HDT/zr6T6F6bn5v0OaKBD4V0iJVB59opHVnqdO+MWWoRc7ENzcBLfoaZXif7n/TOeReKDqE+bVE= Original-Received: by 10.78.25.11 with SMTP id 11mr3458943huy.1163223339034; Fri, 10 Nov 2006 21:35:39 -0800 (PST) Original-Received: by 10.78.198.11 with HTTP; Fri, 10 Nov 2006 21:35:38 -0800 (PST) Original-To: Emacs-Devel Content-Disposition: inline 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:62062 Archived-At: i'm struggling with an interesting coding-system problem presented by allout's topic encryption feature, and wondering whether anyone has suggestions. the problem occurs when non-ascii text, which requires an alternative coding system, exists only within a topic or topics that are encrypted. allout auto-encrypts unencrypted topics, and i can make allout do select-safe-coding-system to promote the proper coding system setting during encryption. the problem is that encryption of the text removes the need for the alternate coding system. when the file is next visited, all the non-ascii characters are encrypted, which is coding-system agnostic. the default coding system is used, and (unless the default happens to be tailored for it) decryption of the topics will deliver the non-ascii text into the wrong coding system. perhaps the thing i'm missing is the right way to save the text so the alternate coding system is recovered despite the absence of any text which requires it. is that possible? might i need to have allout set some local file variable to preserve the coding-system? i think the same problem occurs for whole-buffer encryption, when some of the encrypted text is non-ascii. -- ken ken.manheimer@gmail.com http://myriadicity.net