From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Ulrich Neumerkel Newsgroups: gmane.emacs.devel Subject: Re: Latin-1 non breaking space not highlighted Date: Mon, 15 Apr 2002 01:30:35 +0200 (MET DST) Sender: emacs-devel-admin@gnu.org Message-ID: <200204142330.BAA32503@a0.complang.tuwien.ac.at> NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1018827320 25658 127.0.0.1 (14 Apr 2002 23:35:20 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 14 Apr 2002 23:35:20 +0000 (UTC) Cc: emacs-devel@gnu.org, ulrich@a0.complang.tuwien.ac.at Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16wtWi-0006fj-00 for ; Mon, 15 Apr 2002 01:35:20 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 16wtoA-0003Ts-00 for ; Mon, 15 Apr 2002 01:53: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 16wtUZ-00019w-00; Sun, 14 Apr 2002 19:33:07 -0400 Original-Received: from a0.complang.tuwien.ac.at ([128.130.173.25]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16wtSE-000813-00; Sun, 14 Apr 2002 19:30:43 -0400 Original-Received: (from ulrich@localhost) by a0.complang.tuwien.ac.at (8.9.3/8.9.3) id BAA32503; Mon, 15 Apr 2002 01:30:35 +0200 (MET DST) Original-To: eliz@is.elta.co.il, rms@gnu.org Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:2631 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:2631 > From: "Eli Zaretskii" > I see two possible solutions: > > - hardcode a few more special characters, like ISO8859-x NBSP and a > few Unicode characters; > or > - use syntax tables for non-ASCII characters only, assuming that no > Lisp package does anything weird with their syntax class. Both solutions may cause problems with other/new encoding systems. Maybe better: - use the syntax table of the corresponding fundamental mode