From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Japanese input in Linux environment (fcitx-mozc)
Date: Fri, 09 Jun 2017 12:58:54 +0200 [thread overview]
Message-ID: <87o9txh1g1.fsf@debian.uxu> (raw)
In-Reply-To: f1954aba-a472-a6a8-724e-afe8dfa34ee4@shinoto.de
Maria Shinoto <maria@shinoto.de> writes:
> - Emacs in the terminal works with Japanese
> (fcitx-mozc) flawlessly. - It seems to be a problem
> with GUI Emacs not being able to use fcitx-mozc.
>
> --> I did not test the elder combination ibus-mozc,
> but in winter, when I made my first test series, I had
> the same problem with this combination.
On a bigger note, this is really a *sad day* in Emacs
and all of Gnutopia!
How many people live in China, Japan, and Korea, and
how many use these languages in Asia and all over the
world? And guess what language group will play a huge
role in the future of software development if that
hasn't happened already?
But no matter how good the Asians are/will be it will
never be as classy as the West. Just as Shimano
components (Japan) and Giant frames (Taiwan) pale in
comparison with the Italian and French masters of
Campagnolo and Look. The Queen stays queen - adiós :)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-06-09 10:58 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
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 [this message]
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
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=87o9txh1g1.fsf@debian.uxu \
--to=moasen@zoho.com \
--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.
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).