From: iyzsong@member.fsf.org (宋文武)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Typing on GuixSD in languages other than English
Date: Sat, 09 Apr 2016 09:41:08 +0800 [thread overview]
Message-ID: <87twjbv9sb.fsf@member.fsf.org> (raw)
In-Reply-To: <8760vy9bo3.fsf@gmail.com> (Chris Marusich's message of "Sun, 03 Apr 2016 22:37:48 -0700")
Chris Marusich <cmmarusich@gmail.com> writes:
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> writes:
>
>>> Chris Marusich <cmmarusich@gmail.com> writes:
>>>
>>> The attached patches add anthy and ibus-anthy. They build OK.
>>> However,
>>> Japanese input is not yet working for me. In fact, ibus itself does
>>> not
>>> seem to be working at all.
>>>
>>> How can I verify that ibus is working on its own? I've tried
>>> installing
>>> ibus by itself into my profile. When I do this, I can run ibus-setup,
>>> and I see a "Japanese" language input option. This is true even when
>>> anthy and ibus-anthy are not installed, which surprised me. I had
>>> expected to find no Japanese language input options at all in
>>> ibus-setup
>>> when anthy and ibus-anthy are not installed.
>>>
>>> In GNOME, there is no ibus menu visible anywhere on my screen, so it is
>>> unclear whether ibus is actually working. When I open Gedit and press
>>> <Super>+Space, my input method does not seem to change. According to
>>> ibus-setup, this hotkey should change my input method. However, it
>>> seems like ibus is just not working at all.
>>
>> FWIW, this is what I do on Debian 8 (with GNOME SHELL):
>>
>> - Install ibus, ibus-anthy (or ibus-mozc).
>> - Restart the system.
>> - Go to *System settings → Region & Language*.
>> - Add *Japanese (Anthy)* in Input method.
>
> "Japanese (Anthy)" does not show up as an input method. There are a
> variety of entries (which are present regardless of whether ibus, anthy,
> or ibus-anthy are installed), and none of them mention "Anthy".
>
The exec path in the anthy.xml is wrong, also we need wrap them with
python-pygobject. I fixed that and pushed.
Thanks!
next prev parent reply other threads:[~2016-04-09 1:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 21:51 Typing on GuixSD in languages other than English Chris Marusich
2016-04-03 1:00 ` 宋文武
2016-04-03 4:17 ` Chris Marusich
2016-04-04 0:26 ` Chris Marusich
2016-04-04 2:26 ` Luis Felipe López Acevedo
2016-04-04 5:37 ` Chris Marusich
2016-04-04 14:36 ` Luis Felipe López Acevedo
2016-04-09 1:41 ` 宋文武 [this message]
2016-04-09 19:38 ` Chris Marusich
2016-04-10 9:47 ` 宋文武
2016-04-13 1:48 ` Chris Marusich
2016-04-17 8:26 ` Chris Marusich
2016-04-18 7:27 ` Ricardo Wurmus
2016-04-04 20:10 ` Ricardo Wurmus
2016-04-05 6:48 ` Chris Marusich
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twjbv9sb.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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).