From: Maria Shinoto <maria@shinoto.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Japanese input in Linux environment (fcitx-mozc)
Date: Wed, 7 Jun 2017 08:54:55 +0900 [thread overview]
Message-ID: <c7cca880-1634-ef61-7405-e1bd38c76721@shinoto.de> (raw)
In-Reply-To: <AD840793-B94E-4F12-92AC-B276943C8198@gmail.com>
Dear List members,
a lot of great hints, thank you all. I am living in Japan, it is
morning, and I am following all directions at the moment.
In order to save your time, I write a short summary of the state now,
and hopefully this evening or tomorrow, I can tell you what the result
looks like.
1) The Japanese mailing list just answered, they told me how to use the
Japanese input method from Emacs. It is clumsy, though, they do not
recommend it themselves. Still, I have to test it; I could think of some
additional caveats..
2) The LANG variable seems to be the problem, since I write on a
basically German system with additional keyboard and language input. I
will check this. Basically, I want to stay with a German system and
write multilingual papers in Japanese or English mainly. Will test it
all and report.
I think that sums it up, thanks a lot for now!
Maria
Am 07.06.17 um 08:44 schrieb Jean-Christophe Helary:
>
>> 2017/06/07 0:04、Eli Zaretskii <eliz@gnu.org>のメール:
>>
>>> Can anybody give me a hint into the right direction, how I could use
>>> Emacs with Linux and Japanese?
>>
>> Did you try the Japanese input methods built into Emacs? I don't
>> read or write Japanese, so I don't know how adequate they are.
>
> They are good but require that you remember a method for Emacs and a method for the rest.
>
> Jean-Christophe
>
next prev parent reply other threads:[~2017-06-06 23:54 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7cca880-1634-ef61-7405-e1bd38c76721@shinoto.de \
--to=maria@shinoto.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.