all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Japanese input in Linux environment (fcitx-mozc)
Date: Wed, 7 Jun 2017 10:26:38 +0200	[thread overview]
Message-ID: <20170607082638.GA18108@tuxteam.de> (raw)
In-Reply-To: <20170607080206.GA3070@workstation>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Jun 07, 2017 at 10:02:06AM +0200, Héctor Lahoz wrote:
> Hi. Perhaps this should be a reply to the first mail but I lost it.
> Sorry.
> 
> Just some thoughts about this. This is a very common problem. I wish I
> could offer some specific solution but I can't since I don't write
> Japanese. But I do write Spanish, English, German and occasionally
> Greek and Cyrillic.
> 
> This task, change input between different languages, is not Emacs
> specific. Emacs is not the only application in the world and probably
> other applications will need this too. As I said it is a very common
> task. So it should not be provided by Emacs itself but by some
> underlying system, be it GTK, X11, or even the operating system.
> 
> Emacs should just communicate with that underlying system
> and use its services.
> 
> So I think the right direction is to look at the X input method
> architecture. It seems there are some newer solutions like IBus or
> SCIM. I can't tell how or up to what extent Emacs uses any of these.
> 
> https://en.wikipedia.org/wiki/X_Input_Method

Been there. It's more complicated. Yes, there are upsides to delegating
to X (and when I can, I truly do): entering stuff in a terminal or
a browser works the same than entering stuff in Emacs.

There are downsides too: Emacs input methods are much more flexible,
diverse and easier to set up.

Personally, I try to strong-arm X into doing my thing. That said,
I'm using pretty "plain" X, which is uncommon these days. I never
managed to completely figure out how those things are supposed
to work on more mainstream desktop environments (I support a couple
of Gnome installations). Perhaps I'd be less successful on those.

To sum up: for things I use semi-frequently, I go to the extra
length of "unified" configuration (i.e. outside of Emacs). For
very occasional things, it's Emacs input methods (much easier
to set up).

Sometimes (I started with greek a short while ago), I start with
Emacs, as a pioneer, and then try to rework my setup into a more
unified thing (e.g. setting up a second group by toggling via
double shift).

As for the compose key... for me, it's a boon, but I'd never
recommend it for often-used chars (I type much of German and
am grateful the umlauts got their keys, for example).

Emacs, of course, plays along with everything and then more.
Can't say how grateful I am for *that*

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlk3uL4ACgkQBcgs9XrR2kaZ2gCfdjE/w7abuNajWkgiHB/iQgv1
IuUAn3POpmay1X/bDhnW4Tcmc2/TNtD4
=G1tH
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2017-06-07  8:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  3:24 Japanese input in Linux environment (fcitx-mozc) Maria Shinoto
2017-06-06  5:37 ` Emanuel Berg
2017-06-06  7:40 ` Lee B
2017-06-06 17:40   ` source liu
2017-06-06 15:04 ` Eli Zaretskii
2017-06-06 23:44   ` Jean-Christophe Helary
2017-06-06 23:54     ` Maria Shinoto
2017-06-07  0:08       ` Jean-Christophe Helary
2017-06-07  0:43         ` Emanuel Berg
2017-06-07  1:35           ` Maria Shinoto
2017-06-07  8:02             ` Héctor Lahoz
2017-06-07  8:13               ` Emanuel Berg
2017-06-07  8:26               ` tomas [this message]
2017-06-07  9:24                 ` Emanuel Berg
2017-06-07 11:06                   ` Input methods (Emacs and others), plain X [was: Japanese input in Linux environment] tomas
2017-06-07 14:51                     ` Emanuel Berg
2017-06-07 20:18                       ` tomas
2017-06-07 20:40                         ` Emanuel Berg
2017-06-08  9:12                           ` tomas
2017-06-08 18:37                             ` Emanuel Berg
2017-06-07 15:29               ` Japanese input in Linux environment (fcitx-mozc) Eli Zaretskii
2017-06-09  5:59                 ` Maria Shinoto
2017-06-09  7:53                   ` Emanuel Berg
2017-06-09 10:58                   ` Emanuel Berg
2017-06-09 13:27                   ` Bruce V Chiarelli
2017-06-09 19:49                 ` ISHIKAWA,chiaki
2017-06-09 19:58                   ` ISHIKAWA,chiaki
2017-06-07  5:11           ` Jean-Christophe Helary
2017-06-07  6:26             ` Emanuel Berg
2017-06-07  7:02               ` tomas
2017-06-07  7:17                 ` Emanuel Berg
  -- strict thread matches above, loose matches on Subject: below --
2017-06-06  4:53 Priv.-Doz. Dr. M. Shinoto

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170607082638.GA18108@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.