From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: composed characters question and suggestions for quail-cyrillic-* Date: Wed, 09 Jul 2008 17:14:01 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <863ami4seu.fsf@lifelogs.com> References: <86lk19mmua.fsf@lifelogs.com> <485298A4.30000@gnu.org> <867ict8awn.fsf@lifelogs.com> <87zlouswvk.fsf@jurta.org> <86skulfo7j.fsf@lifelogs.com> <87fxql8j7y.fsf@jurta.org> <86y74ccrp4.fsf@lifelogs.com> <87od583s2a.fsf@jurta.org> <86wsjv6o6i.fsf@lifelogs.com> <868wwa7v1k.fsf@lifelogs.com> <87prpmc011.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1215641418 13258 80.91.229.12 (9 Jul 2008 22:10:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Jul 2008 22:10:18 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 10 00:11:05 2008 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.50) id 1KGhsN-0008CX-3F for ged-emacs-devel@m.gmane.org; Thu, 10 Jul 2008 00:11:03 +0200 Original-Received: from localhost ([127.0.0.1]:45683 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KGhrU-0004FK-23 for ged-emacs-devel@m.gmane.org; Wed, 09 Jul 2008 18:10:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KGhrP-0004CA-6t for emacs-devel@gnu.org; Wed, 09 Jul 2008 18:10:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KGhrM-0004AV-H4 for emacs-devel@gnu.org; Wed, 09 Jul 2008 18:10:02 -0400 Original-Received: from [199.232.76.173] (port=46145 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KGhrM-0004AP-DL for emacs-devel@gnu.org; Wed, 09 Jul 2008 18:10:00 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:33085 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KGhrL-0003eh-7z for emacs-devel@gnu.org; Wed, 09 Jul 2008 18:10:00 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KGhrD-0004QX-Pv for emacs-devel@gnu.org; Wed, 09 Jul 2008 22:09:51 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Jul 2008 22:09:51 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Jul 2008 22:09:51 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 103 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:r+O7NseSvv4G6i/brgQQfAPZfyY= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:100505 Archived-At: On Wed, 09 Jul 2008 22:33:38 +0300 Juri Linkov wrote: TZ> OK, I changed things accordingly and will commit to CVS when the problem TZ> above with doing combining characters in Quail is resolved. >> >> This is the only thing stopping me. I adjusted the accents and added >> some more special characters; here's the special characters with some >> comments. >> >> ("/c" ?©) >> ("/tm" ?®) ;; I couldn't find a TM glyph in Unicode JL> It is ?\u2122. JL> It is ?\u2122. OK, I changed to: ("/tm" ?™) ("/reg" ?®) >> ("/kop" ?к) ;; not sure JL> No Unicode character, and never will be I guess. Probably not worth the trouble then. Same for rubles, leva, and stotinki, their symbols are currently trivial so I'll remove them. The situation is different for Roman numerals which have distinct code points from the corresponding ASCII characters. I'm not including lowercase versions but I could (downcase-region is so nice, this took 2 seconds): ("/i" ?ⅰ) ("/ii" ?ⅱ) ("/iii" ?ⅲ) ("/iv" ?ⅳ) ("/v" ?ⅴ) ("/vi" ?ⅵ) ("/vii" ?ⅶ) ("/viii" ?ⅷ) ("/ix" ?ⅸ) ("/x" ?ⅹ) ("/xi" ?ⅺ) ("/xii" ?ⅻ) I don't recall them being used for anything, but then again it's been a while since I wrote in Bulgarian every day, and Russian and others may want them. >> I often see it written as q or u in manually transliterated text. Maybe >> // or /q or /u would work? The corresponding /? /Q /U would uppercase it. JL> I've never seen it written as q or u. And indeed there is no such rule JL> on http://en.wikipedia.org/wiki/Translit or on this page in other JL> languages (Bulgarian, Russian) where q is used for ю, and q for я. It's ad hoc I guess. No matter. JL> One possible letter for ь is x. I guess it is from jcuken-only JL> keyboards, but since it is already taken for x in cyrillic-translit, JL> maybe we should replace the rule ("x" ?х) with ("x" ?ь)? OK, ditto for X -> Ь. We'll be lynched, surely. JL> I like your current set of rules, they are easy to remember and input. JL> But I have doubts about << and >> since they are inconsistent with JL> other sequences with the leading slash. Yes, but it's very rare to need << or >> in any other context. Let's try it, I'm sure only shell users will complain :) At worst you have to do C-\ Shift-, Shift-, C-\ to get the regular << meaning. Compared to / Shift-, Shift-, / Shift-. Shift-. all the time while typing, I think it's better. JL> Since these rules will be needed in parallel with other input methods, JL> I suggest you to create two separate input methods: one with the name JL> like `typographic' (if you are going to provide only typographic JL> characters) for rules without the leading slash and `typographic-pre' JL> for rules with the leading slash. And with the code Handa-san provided JL> it will be possible to activate multiple input methods. When that code is in the CVS trunk I can do that, but I'm not convinced having two methods (with/without prefix) would be any better than a single common one. A single method means less to remember, less to confuse the user. JL> Then how about the following rules: JL> /. "․" U2024 # ONE DOT LEADER JL> /.. "‥" U2025 # TWO DOT LEADER JL> /... "…" ellipsis # HORIZONTAL ELLIPSIS Added also. Ted