From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chip Coldwell Newsgroups: gmane.emacs.devel Subject: Re: regex encoding Date: Tue, 1 Aug 2006 16:40:32 -0400 (EDT) Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1390428003-1154464832=:2363" X-Trace: sea.gmane.org 1154464871 18552 80.91.229.2 (1 Aug 2006 20:41:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 1 Aug 2006 20:41:11 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 01 22:41:03 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 1G812n-0004Fg-On for ged-emacs-devel@m.gmane.org; Tue, 01 Aug 2006 22:40:50 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G812m-00058Y-WF for ged-emacs-devel@m.gmane.org; Tue, 01 Aug 2006 16:40:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G812X-00057G-6p for emacs-devel@gnu.org; Tue, 01 Aug 2006 16:40:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G812W-00055p-8W for emacs-devel@gnu.org; Tue, 01 Aug 2006 16:40:32 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G812W-00055T-2N for emacs-devel@gnu.org; Tue, 01 Aug 2006 16:40:32 -0400 Original-Received: from [66.187.233.31] (helo=mx1.redhat.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G815T-00045x-KM for emacs-devel@gnu.org; Tue, 01 Aug 2006 16:43:35 -0400 Original-Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k71KeTns029510; Tue, 1 Aug 2006 16:40:29 -0400 Original-Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k71KeTqA031937; Tue, 1 Aug 2006 16:40:29 -0400 Original-Received: from dhcp83-29.boston.redhat.com (dhcp83-29.boston.redhat.com [172.16.83.29]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id k71KeTw4009637; Tue, 1 Aug 2006 16:40:29 -0400 Original-To: Reiner Steib In-Reply-To: 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:57967 Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1390428003-1154464832=:2363 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx1.redhat.com id k71KeTns029510 On Tue, 1 Aug 2006, Chip Coldwell wrote: > On Tue, 1 Aug 2006, Reiner Steib wrote: >>=20 >> | [a-zA-Z=C4=D6=DC=E4=F6=DF=FC] >>=20 >> If you intend to send UTF-8, you MUA should not declare it as >> "Content-Type: TEXT/PLAIN; charset=3DISO-8859-1". ;-) > > Ooops. I haven't tamed my MUA yet. It's only been ten years. > >>> My question is: are emacs regex character classes limited to the >>> iso-8859-1 character set, or is there some way to represent Unicode >>> (such as UTF-8) characters in a character class? >>=20 >> AFAIK, you can write the chars in UTF-8 if you specify the encoding of >> the lisp file, cf. (info "(emacs)Specify Coding"): >>=20 >> --8<---------------cut here---------------start------------->8--- >> ;; -*- coding: utf-8 -*- >> (defun rs-test () >> (interactive) >> (re-search-forward "[=C4=D6=DC=E4=F6=DF=FC]")) >> --8<---------------cut here---------------end--------------->8--- >>=20 >> I don't know if there's a reason why isn't used in `ispell.el'. > > The particular issue is that ispell is currently broken if your LANG > environment variable specifies UTF-8 encoding, your buffer is UTF-8 > encoded and contains one of these non-ASCII characters, and you > specify the "deutsch8" dictionary. ispell-word generates the error: > > "Ispell and its process have different character maps" I should also mention that this is with aspell version 0.6; version 0.5 seems to do the right thing regardless. Chip --=20 Charles M. "Chip" Coldwell Senior Software Engineer Red Hat, Inc 978-392-2426 --8323328-1390428003-1154464832=:2363 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --8323328-1390428003-1154464832=:2363--