From: Juri Linkov <juri@jurta.org>
To: Vasily Korytov <vasily@korytov.pp.ru>
Cc: 904@emacsbugs.donarmstrong.com
Subject: bug#904: [patch] russian-typewriter input method does not follow actual layout
Date: Sat, 05 Dec 2009 02:51:41 +0200 [thread overview]
Message-ID: <87skbqtf8i.fsf@mail.jurta.org> (raw)
In-Reply-To: <87wshpusjc.fsf@dub.dyndns.ws> (Vasily Korytov's message of "Sat, 06 Sep 2008 20:51:19 +0400")
> But Emacs 22.2 has own standard for `russian-typewriter' input method.
> Probably, borrowed from some other map. Indeed, there're a lot of
> variations of `Russian Typewriter' implementation, a real mess.
>
> In fact, I've already seen on the Net some Lisp files to implement a
> correct typewriter layout (at least, in the number keys region) in
> Emacs.
>
> The patch, I'm proposing, makes `russian-typewriter' method behave like
> a real Russian typewriter (except § key) or a Russian computer. I think,
> it's better to fix the problem, that making users of
> `russian-typewriter' implement a custom input method.
I suggest to install this patch to close bug#904. I confirm it implements
a layout used on real typewriters.
However, the layout it replaces is useful as well. So I suggest
to move the current "russian-typewriter" layout to its current alias
"cyrillic-jcuken" (thus avoiding tricks employed to define the input
method's alias).
Installing this patch also requires updating `input-method' properties
in lisp/language/cyrillic.el (and removing some FIXME's). I believe this
would clean up the mess.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-12-05 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fx7q5dtu.fsf@stupidchicken.com>
2008-09-06 16:51 ` bug#904: [patch] russian-typewriter input method does not follow actual layout Vasily Korytov
2009-12-05 0:51 ` Juri Linkov [this message]
2009-12-05 5:10 ` Stefan Monnier
2009-12-05 3:05 ` bug#904: marked as done ([patch] russian-typewriter input method does not follow actual layout) Emacs bug Tracking System
2009-12-05 3:14 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skbqtf8i.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=904@emacsbugs.donarmstrong.com \
--cc=vasily@korytov.pp.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).