Project

General

Profile

Bug #16719

Switch from ibus-anthy to Mozc

Added by mercedes508 11 months ago. Updated 25 minutes ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
feature/16719-ibus-mozc
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Hey received a bug report from a japanese user, complaining about our current input method for japanese.

Here are a few reason why it would be better to switch to fcitx-mozc:

  • the accuracy of the conversion of Anthy to Kanji is so bad that the amount of
    kanji that can be converted is small, so it is useless
  • most japanese users use mozc

And in order to use this piece of software one has to reboot Tails after installing, so adding it through additional software doesn't do the trick.


Related issues

Duplicated by Tails - Bug #17389: Update japanese input method to uim-mozc Duplicate

Associated revisions

Revision c56cd06b (diff)
Added by intrigeri 6 days ago

Switch Japanese input method from Anthy to Mozc (refs: #16719)

A Japanese speaker (passis12345678) tells us that:

"I don't think any Japanese users would agree that Anthy is better than Mozc.
The accuracy of Mozy's Kanji conversion is clearly superior to that of Anthy.
I’ve never seen or heard of anyone who likes Anthy.
Any Japanese user would be happy to replace Anthy with Mozc."

They also note that ibus-anthy has one advantage over ibus-mozc: it defaults to
Japanese input, while ibus-mozc defaults to alphabetic and the user has to
change the setting to Japanese every time they login. Despite that drawback,
passis12345678 thinks that switching to Mozc is worth it anyway: it's
a one-per-Tails-session annoyance, as opposed to a permanent annoyance while
typing in Japanese.

This would be fixed by fcitx-mozc (which defaults to Japanese), but switching to
fcitx is another, much bigger matter: IBus seems to be much better integrated
into GNOME than fcitx. Let's stick to IBus for now and try this minimal change.

History

#1 Updated by intrigeri 11 months ago

  • Assignee changed from sajolida to intrigeri

I'll take a look as I've done work in this very area recently.

Note that we don't ship ibus-mozc so I'll fix this ticket's title once I'm there.

#2 Updated by intrigeri 10 months ago

  • Subject changed from Switch from ibus-mozc to fcitx-mozc to Switch from ibus-anthy to fcitx-mozc
  • Description updated (diff)
  • Category deleted (Accessibility)

#3 Updated by intrigeri 10 months ago

  • Subject changed from Switch from ibus-anthy to fcitx-mozc to Switch from ibus-anthy to Mozc
  • Assignee deleted (intrigeri)

We could try shipping ibus-mozc (either on top of ibus-anthy or instead of it), even though I'm not entirely convinced by the current state of its maintenance in Debian. My concern is that last time I tried to get feedback about such matters, I got very little, so I'm a bit afraid of making things worse for some users while satisfying some users' preferences. @mercedes508, can you please share (privately) the email address of this user, so I can at least ask them whether whatever we prepare is better for them than the status quo?

fcitx is a totally different beast and it has no IBus compatibility in Stretch (while there's fcitx5-module-ibus in Buster but that seems pretty much experimental at this point, no idea how well this would integrate with a GNOME desktop).

#4 Updated by mercedes508 10 months ago

intrigeri wrote:

@mercedes508, can you please share (privately) the email address of this user, so I can at least ask them whether whatever we prepare is better for them than the status quo?

Done.

#5 Updated by passis12345678 9 months ago

Hi, I am the Japanese user.
I don't use the email address anymore, so I'll answer it here.

There are several types of Japanese input, and of course there are preferences.
But I don't think any Japanese users would agree that Anthy is better than Mozc.
The accuracy of Mozy's Kanji conversion is clearly superior to that of Anthy.
I’ve never seen or heard of anyone who likes Anthy.
Any Japanese user would be happy to replace Anthy with Mozc.

Replacing ibus-anthy with ibus-mozc is just one thing that can get worse. That's an extra step to start using Japanese input.
ibus-anthy allows you to enter Japanese immediately after booting, but ibus-mozc defaults to alphabetic and you have to change the setting to Japanese each time after booting.
That is why I think fcitx-mozc is better than ibus-mozc. fcitx-mozc doesn't do that. You can input Japanese immediately after starting.

So fcitx-mozc is best, but I think ibus-mozc also has advantages over disadvantages.
This is because the inconvenience of changing settings each time is only once after you start up Tails, but the inconvenience of poor Kanji conversion accuracy lasts all the time you start up Tails.

#6 Updated by intrigeri 3 months ago

  • Duplicated by Bug #17389: Update japanese input method to uim-mozc added

#7 Updated by goupille 2 months ago

@intrigeri, I just sent you an email (ticket number in the subject) with the contact of a user very willing to help for this

#9 Updated by intrigeri 6 days ago

  • Status changed from Confirmed to In Progress
  • Assignee set to intrigeri
  • Target version set to Tails_4.6
  • Feature Branch set to feature/16719-ibus-mozc

#10 Updated by intrigeri 6 days ago

Hi @passis12345678,

it took me a while to find a little bit of spare volunteer time to get to this, but I have finally prepared a Tails experimental image with Mozc:

https://nightly.tails.boum.org/build_Tails_ISO_feature-16719-ibus-mozc/lastSuccessful/archive/build-artifacts/

Could you please try it?

Thanks in advance!

Note that it's using ibus-mozc, instead of fcitx-mozc, because IBus is better integrated with GNOME. I suspect there's a way to pre-configure ibus-mozc to use one of the Japanese input methods (instead of latin) it supports, but I did not research this; and I would not know which one to pick as a default anyway.

Note to myself: I've also asked the user mentioned on #16719#note-8 to try it.

#11 Updated by passis12345678 about 8 hours ago

Hi intrigeri,

I tried

and


.

I couldn't start that ISO file. But I could start that IMG file and I was able to use Mozc without trouble.

The only problem with ibus-mozc is that the default characters are Latin instead of Japanese, but I found a solution and I hope you can check it out.This is a very short page in English.

Here's the page.
https://github.com/google/mozc/issues/381

Thank you so much for taking the time to improve the Japanese language. Japanese users will be delighted.

#12 Updated by intrigeri about 7 hours ago

Hi @passis12345678,

I tried

[...]
I was able to use Mozc without trouble.

Thanks a lot for the quick feedback!

The only problem with ibus-mozc is that the default characters are Latin instead of Japanese,

From #16719#note-5 I understood that this one-per-Tails-session annoyance (Mozc) was preferable to the permanent annoyance while typing in Japanese caused by Anthy.
From this I inferred that the state of the branch you've tested is an improvement compared to current Tails releases.
Did I understood correctly?

If we're on the same page, then I'll propose the current branch for Tails 4.6, without blocking on this problem.

but I found a solution and I hope you can check it out.
[…]
https://github.com/google/mozc/issues/381

Unfortunately, this suggests that there's no way to configure this: the proposed solution requires patching and recompiling ibus, which I think requires a bit too much maintenance work.

Thank you so much for taking the time to improve the Japanese language. Japanese users will be delighted.

My pleasure :)

#13 Updated by passis12345678 25 minutes ago

Yes. You completely understand.
I think the new problem created by replacing ibus-anthy with ibus-mozc will create new frustration among Japanese users. But if you asked those people if they should quit ibus-mozc and go back to ibus-anthy, I'm sure they wouldn't agree, and I think the benefits of mozc are as great as the heavy users of tails.
I'm going to use this test image for a while as I can't wait for 4.6 to be released.

Also available in: Atom PDF