From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: handa Newsgroups: gmane.emacs.devel Subject: Re: Entering Unicode characters Date: Sat, 30 Jan 2016 21:16:46 +0900 Message-ID: <8760yb9s9d.fsf@gnu.org> References: <83d1skxt0i.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1454156271 30960 80.91.229.3 (30 Jan 2016 12:17:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 30 Jan 2016 12:17:51 +0000 (UTC) Cc: jean.christophe.helary@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 30 13:17:45 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 1aPUT0-0000k6-Dx for ged-emacs-devel@m.gmane.org; Sat, 30 Jan 2016 13:17:26 +0100 Original-Received: from localhost ([::1]:38464 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aPUSz-0006FG-NN for ged-emacs-devel@m.gmane.org; Sat, 30 Jan 2016 07:17:25 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37618) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aPUSl-0006Ey-B0 for emacs-devel@gnu.org; Sat, 30 Jan 2016 07:17:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aPUSk-0005ng-72 for emacs-devel@gnu.org; Sat, 30 Jan 2016 07:17:11 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39455) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aPUSe-0005gM-6B; Sat, 30 Jan 2016 07:17:04 -0500 Original-Received: from fl1-110-233-34-83.iba.mesh.ad.jp ([110.233.34.83]:43118 helo=shatin) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aPUSS-0004UI-DR; Sat, 30 Jan 2016 07:17:01 -0500 Original-Received: from handa by shatin with local (Exim 4.86) (envelope-from ) id 1aPUSN-0003z1-24; Sat, 30 Jan 2016 21:16:47 +0900 In-Reply-To: <83d1skxt0i.fsf@gnu.org> (message from Eli Zaretskii on Fri, 29 Jan 2016 18:14:21 +0200) 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:199036 Archived-At: In article <83d1skxt0i.fsf@gnu.org>, Eli Zaretskii writes: > > Most input methods are deterministic, i.e. the defined key sequence > > reaches to a target character (or a string), but Chinese input methods > > are not deterministic, i.e. the defined key sequence reaches only to a > > group of candidate characters. A user has to select one of them by arr= ow > > keys or by an index number. So, for such an input method, showing > > candidate characters is mandatory. > So you are saying that the candidates are shown only when selection is > done by typing a digit? Not exactly. The selection can also be done by C-f C-b C-n C-p and arrow keys. Anyway, candidates are shown only when an input method doesn't define an exact key sequence to input a specific character. Chinese-py only defines that "ni" is for inputting one of "=E4=BD=A0=E5=91= =A2=E5=B0=BC=E6=B3=A5=E9=80=86=E5=80=AA =E5=8C=BF=E6=8B=9F=E8=85=BB=E5=A6=AE=E9=9C=93=E6=98=B5=E6=BA=BA=E6=97=8E=E7= =9D=A8=E9=B2=B5=E5=9D=AD=E7=8C=8A=E6=80=A9=E4=BC=B2=E7=A5=A2=E6=85=9D=E9=93= =8C". How many of those candidates are shown depending on your window width. If the width is too short to show all candidates, a user have to type arrow keys or C-n, C-p, C-f, C-b to see all candidates. In that sense, chinese-py is non-deterministic. > Can we add an optional feature where the candidates will be shown even > in deterministic input methods, although the way to choose the > candidates is not by typing a digit? For example: > a["'/^_`~] " - =C3=A4 ' - =C3=A1 / - =C3=A5 ^ - =C3=A2 _ - =C2=AA = ` - =C3=A0 ~ - =C3=A3 > or something similar? Of course adding such a feature is possible, but it's not just a changing of condition of some code, but a completely new feature. The code to get "=E4=BD=A0=E5=91=A2=E5=B0=BC=E6=B3=A5=E9=80=86=E5=80=AA=E5=8C= =BF=E6=8B=9F=E8=85=BB=E5=A6=AE=E9=9C=93=E6=98=B5=E6=BA=BA=E6=97=8E=E7=9D=A8= =E9=B2=B5=E5=9D=AD=E7=8C=8A=E6=80=A9=E4=BC=B2=E7=A5=A2=E6=85=9D=E9=93=8C" w= hen a user type "ni" is easy because chinese-py directly defines it. But to get "=C3=A4=C3=A1=C3=A5=C3=A2=C2=AA=C3=A0=C3=A3" when a user type "a" requires = completely different code. I can work on it, but it may take time. --- K. Handa handa@gnu.org