From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Entering Unicode characters Date: Sat, 30 Jan 2016 09:30:56 +0200 Message-ID: <834mdvy15b.fsf@gnu.org> References: <878u389yfl.fsf@gnu.org> <83d1skxt0i.fsf@gnu.org> <52F3C008-1B3B-4ACD-B74A-52E19F1E6369@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1454139100 16811 80.91.229.3 (30 Jan 2016 07:31:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 30 Jan 2016 07:31:40 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 30 08:31:35 2016 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 1aPQ0L-00036i-9i for ged-emacs-devel@m.gmane.org; Sat, 30 Jan 2016 08:31:33 +0100 Original-Received: from localhost ([::1]:37793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aPQ0K-0003Fj-GY for ged-emacs-devel@m.gmane.org; Sat, 30 Jan 2016 02:31:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50212) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aPQ0H-0003Ei-E8 for emacs-devel@gnu.org; Sat, 30 Jan 2016 02:31:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aPQ0E-0005Po-7k for emacs-devel@gnu.org; Sat, 30 Jan 2016 02:31:29 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34219) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aPQ0E-0005Pk-3z; Sat, 30 Jan 2016 02:31:26 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1232 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aPQ0D-0003Tl-Hv; Sat, 30 Jan 2016 02:31:25 -0500 In-reply-to: <52F3C008-1B3B-4ACD-B74A-52E19F1E6369@gmail.com> (message from Jean-Christophe Helary on Sat, 30 Jan 2016 12:03:12 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:199025 Archived-At: > From: Jean-Christophe Helary > Date: Sat, 30 Jan 2016 12:03:12 +0900 > > Although what I am discussing here is strictly related to current input systems and not to a the new capability that Richard desires, I think the bigger issue here is first discoverability and then input method. > > turkish-postfix offers discoverability for "i". chinese-py offers discoverability for all its characters (presumably), neither latin-1-postfix not latin-1-prefix offer any sort of discoverability and also lack predictability (why does /e= œ but /E=Æ ?, also, when you shift to french-prefix you actually do not get all the characters that you could possibly type in French - ±÷ªº¥°½¾¼ etc. - even though french should be a subset of latin-1, with the exception of œ/Œ.) > > Then there is the input method when you have discovered the character you want to enter. I personally think that offering 2 options when possible (composing character *and* digit) is the best. Composing characters, and in the case of chinese-py we can argue that letters *are* composing characters for all practical purposes, are available for characters that are input frequently by a given user, and digits are there to input the occasional character. There is no logical need to not have a digit based input for composed characters. Yes, the area of input methods in Emacs needs some long-term loving care. They only rarely get any attention, so most methods stay as they were submitted years ago, and some are no longer up-to-date with the changes in people expectations. Would you like to work on making the Emacs input methods better? Thanks.