From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Feature freeze on October 1 Date: Sun, 23 Sep 2012 11:05:12 +0900 Message-ID: <87haqp1okn.fsf@gnu.org> References: <83ehlvy2ec.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348365953 17091 80.91.229.3 (23 Sep 2012 02:05:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Sep 2012 02:05:53 +0000 (UTC) Cc: cyd@gnu.org, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 23 04:05:57 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 1TFba1-0002iX-7N for ged-emacs-devel@m.gmane.org; Sun, 23 Sep 2012 04:05:57 +0200 Original-Received: from localhost ([::1]:55266 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFbZw-000419-AQ for ged-emacs-devel@m.gmane.org; Sat, 22 Sep 2012 22:05:52 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:58369) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFbZq-00040N-5M for emacs-devel@gnu.org; Sat, 22 Sep 2012 22:05:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TFbZl-0002Qm-8H for emacs-devel@gnu.org; Sat, 22 Sep 2012 22:05:46 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:51999) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFbZk-0002Qi-Sa for emacs-devel@gnu.org; Sat, 22 Sep 2012 22:05:41 -0400 Original-Received: from 253.240.accsnet.ne.jp ([202.220.240.253]:51577 helo=mongkok) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1TFbZT-0005aZ-Ky; Sat, 22 Sep 2012 22:05:40 -0400 In-Reply-To: <83ehlvy2ec.fsf@gnu.org> (message from Eli Zaretskii on Fri, 21 Sep 2012 15:40:59 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 208.118.235.10 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:153477 Archived-At: Very sorry for the late response on this matter. In article <83ehlvy2ec.fsf@gnu.org>, Eli Zaretskii writes: > > From: Stefan Monnier > > Cc: handa@gnu.org, cyd@gnu.org, emacs-devel@gnu.org > > Date: Mon, 17 Sep 2012 15:36:42 -0400 > > > > >> AFAIK unification is already performed when we read a char from > > >> outside Emacs > > > Where does that happen in the code? > > > > I assume it's done in the coding-system's decoding code. Yes. > But that doesn't get run (or at least not always) when a character is > typed on the keyboard, does it? E.g., on MS-Windows characters are > read directly in Unicode when possible. I'm sure Emacs does something > like that on X as well. > So it looks like some un-unified characters can still sneak into the > buffer. On X, Emacs uses X input method which returns characters encoded in the current locale, and thus Emacs decodes them by Vlocale_coding_system. So, the unification should be done here too. > > so maybe all it takes is to remove the maybe_unify_char thingy? > Not sure that's all. I hope Handa-san could outline the plan for > attacking this problem, then maybe I could work on at least part of > that, if not all of it. I have not yet figured out in detail the effect, but, what should be done, I think, is to remove the call of MAYBE_UNIFY_CHAR in char_string and string_char of character.c. --- Kenichi Handa handa@gnu.org