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: highlighting non-ASCII characters Date: Mon, 29 Mar 2010 16:19:07 -0400 Message-ID: References: <6932BBFEB09A4BA09156ED7F598569CE@us.oracle.com> <87pr2uv8e1.fsf@lifelogs.com> <87aatyuj9s.fsf@lifelogs.com> <87pr2rj89j.fsf@lifelogs.com> <87ljdeke5k.fsf@lifelogs.com> <87eij3ht2c.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1269895214 29539 80.91.229.12 (29 Mar 2010 20:40:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 29 Mar 2010 20:40:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 29 22:40:06 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NwLkj-00040q-Jp for ged-emacs-devel@m.gmane.org; Mon, 29 Mar 2010 22:40:05 +0200 Original-Received: from localhost ([127.0.0.1]:38786 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NwLkg-00021r-W3 for ged-emacs-devel@m.gmane.org; Mon, 29 Mar 2010 16:40:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NwLTn-0000yP-Li for emacs-devel@gnu.org; Mon, 29 Mar 2010 16:22:35 -0400 Original-Received: from [140.186.70.92] (port=34177 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NwLTl-0000qu-RD for emacs-devel@gnu.org; Mon, 29 Mar 2010 16:22:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NwLQS-0002Fr-G1 for emacs-devel@gnu.org; Mon, 29 Mar 2010 16:19:09 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:47771 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NwLQS-0002Fe-Ce for emacs-devel@gnu.org; Mon, 29 Mar 2010 16:19:08 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAIuosEtLd/h9/2dsb2JhbACbJXK/Y4UBBIse X-IronPort-AV: E=Sophos;i="4.51,330,1267419600"; d="scan'208";a="59761025" Original-Received: from 75-119-248-125.dsl.teksavvy.com (HELO pastel.home) ([75.119.248.125]) by ironport2-out.pppoe.ca with ESMTP; 29 Mar 2010 16:19:07 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 376B485F0; Mon, 29 Mar 2010 16:19:07 -0400 (EDT) In-Reply-To: <87eij3ht2c.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 29 Mar 2010 13:38:19 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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:122874 Archived-At: > Yes, probably. But that's accidental. I still think the character > classes [:idn:] (revised name from before) and [:confusable:] (or > [:homoglyph:]) would make sense as a first step, then we can decide how > to highlight them. The homoglyph data would be a useful starting point for the feature I imagine, indeed. But from the message that started this thread, "K" is a homoglyph, yet highlighting it everywhere doesn't sound like a good idea, so basically we need to associate with each homoglyph char a context where it is expected and only highlight it when it appears in a different context (or maybe rather when it appears in the context of its peer). Stefan