From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Ispell and unibyte characters Date: Sun, 15 Apr 2012 22:40:29 -0400 Message-ID: References: <83aa3f2hgh.fsf@gnu.org> <20120326173912.GA22306@agmartin.aq.upm.es> <20120328191821.GA6266@agmartin.aq.upm.es> <20120410190803.GA13517@agmartin.aq.upm.es> <83ty0r5rmd.fsf@gnu.org> <20120412143657.GA18352@agmartin.aq.upm.es> <83d37c4vw5.fsf@gnu.org> <20120413152525.GA14949@agmartin.aq.upm.es> <20120413184401.GA17992@agmartin.aq.upm.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1334546678 18693 80.91.229.3 (16 Apr 2012 03:24:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 16 Apr 2012 03:24:38 +0000 (UTC) Cc: emacs-devel@gnu.org To: Agustin Martin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 16 05:24:37 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SJcYK-0002r4-6K for ged-emacs-devel@m.gmane.org; Mon, 16 Apr 2012 05:24:32 +0200 Original-Received: from localhost ([::1]:33060 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SJcYJ-0000JF-M8 for ged-emacs-devel@m.gmane.org; Sun, 15 Apr 2012 23:24:31 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:39195) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SJcYF-0000J5-N4 for emacs-devel@gnu.org; Sun, 15 Apr 2012 23:24:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SJcYD-0000ee-5o for emacs-devel@gnu.org; Sun, 15 Apr 2012 23:24:27 -0400 Original-Received: from ironport-out.teksavvy.com ([206.248.143.162]:23892) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SJcYD-0000cb-1P for emacs-devel@gnu.org; Sun, 15 Apr 2012 23:24:25 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApYIACxOgk9FpZiF/2dsb2JhbABDuCMDgQyBCIIJAQEEAVYjBQsLNBIUGA0kiBwFtjKLYYR5BKRFgV2DAw X-IronPort-AV: E=Sophos;i="4.75,391,1330923600"; d="scan'208";a="174515251" Original-Received: from 69-165-152-133.dsl.teksavvy.com (HELO pastel.home) ([69.165.152.133]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 15 Apr 2012 22:40:30 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id C3511580D8; Sun, 15 Apr 2012 22:40:29 -0400 (EDT) In-Reply-To: (Agustin Martin's message of "Sun, 15 Apr 2012 02:02:11 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.143.162 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:149683 Archived-At: > Imagine Catalan dictionary with iso-8859-1 "=B7" in otherchars and other > dictionary (I am guessing the possibility to be more general, do not > actually have a real example of something different from our Debian > file with all info put together) with another upper char in > otherchars, but in a different encoding (e.g., koi8r). You're still living in Emacs-21/22: since Emacs-23, basically chars aren't associated with their encoding (actually charset) any more. > The only possibility to have both coexist as chars in the same file is > to use multibyte UTF-8 chars instead of mixed unibyte iso-8859-1 and > koi8r, so Emacs properly gets chars when reading the file (if properly > guessing file coding-system). Not at all, there are many encodings which cover the superset of iso-8859-* and koi8-*. UTF-8 is the more fashionable one nowadays, but not anywhere close to the only one. e.g. there's also iso-2022, emacs-mule, and then some. > I'd however use this only in personal ~/.emacs files and if needed. Why? It would make the code more clear and simpler. > That is true for files with a single encoding. However, the problem > happens when a file has mixed encodings like in the Debian example I > mentioned. I know, this will not happen in real manually edited files, > but can happen and happens in aggregates like the one I mentioned. That's an old solved problem. > If file is loaded with a given coding-system-for-read chars in that > coding-system will be properly interpreted by Emacs when reading, but > not the others. Something like that happened with > iso-8859-1/iso-8859-15 chars in That was then. Not any more. Stefan