From: source liu <sourceonly@gmail.com>
To: Lee B <lboc.home@gmail.com>
Cc: help-gnu-emacs@gnu.org, Maria Shinoto <maria@shinoto.de>
Subject: Re: Japanese input in Linux environment (fcitx-mozc)
Date: Tue, 6 Jun 2017 11:40:51 -0600 [thread overview]
Message-ID: <CAAzVxgMmuw2LE-PUumr9t0zjuc+YwoT_bmbt1y575s9vc0hfoA@mail.gmail.com> (raw)
In-Reply-To: <m2vao9o971.fsf@gmail.com>
Hi,
1. So, the fcitx is OK with the Desktop Environment?
2. if 1, please try emacs -nw under a terminal to see if the input works.
3. if 2 works, please export LANG to you japanese LANG, IE. export
LANG=ja_jp.UTF-8 rather than en_US.UTF-8, then start emacs and try
again.
to my experience, emacs would ignore fcitx or ibus if the LANG is set
to en_US.UTF-8, but even though, emacs -nw under the terminal would do
the trick, or just set the LANG before start emacs
you can have a try.
On Tue, Jun 6, 2017 at 1:40 AM, Lee B <lboc.home@gmail.com> wrote:
> On 火, 6 06 2017, Maria Shinoto wrote:
>
>> Hi,
>>
>> I have been using a Mac over decades, but now I am preparing for a
>> change to Linux, testing all software and setups on an old Lenovo
>> Thinkpad with LinuxMint 18.1.
>>
>> Emacs does not accept the Japanese input with fcitx-mozc, and there
>> are some forum posts from which I could only learn that "it sucks". I
>> did not found anything helpful.
>>
>> Can anybody give me a hint into the right direction, how I could use
>> Emacs with Linux and Japanese?
>>
>> Thanks,
>> Maria
>
> I use ibus and mozc on Debian with no problems. Never used Mint, I'm afraid.
>
> Lee.
>
--
Liu An
Institution of modern physics, Shanghai, China
next prev parent reply other threads:[~2017-06-06 17:40 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 [this message]
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
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=CAAzVxgMmuw2LE-PUumr9t0zjuc+YwoT_bmbt1y575s9vc0hfoA@mail.gmail.com \
--to=sourceonly@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lboc.home@gmail.com \
--cc=maria@shinoto.de \
/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).