https://bugs.kde.org/show_bug.cgi?id=511561

Jumpei Ogawa <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|REPORTED                    |CONFIRMED

--- Comment #3 from Jumpei Ogawa <[email protected]> ---
Translation of the reply from shoutarou:

Thank you for your reply.

> 1. Which IME are you using?

I use ATOK2016 for Japanese input.

> 2. Can you check if this issue still occurs when you temporarily switch your 
> IME to MS-IME?

When I switched to MS-IME and attempted to input Japanese, I was able to enter
Japanese characters correctly.
After that, I switched to ATOK2016 to type Japanese again, but Krita crashed.
It is reproducible.
I understand Krita Ver.5.2.13 and ATOK2016 might have a compatibility issue.

I have used ATOK2016 since I was using Windows8.1, and there were no problem in
using Krita on it.
The old version of Krita didn't have such a bug.
I assumed that I could use Krita as well, and I never thought the Japanese IME
can cause such an issue.


Thanks to your advice, I could find the cause.
I will use MS-IME when I type Japanese.
At the moment, my problem has been resolved.
Thank you for the help from the developers and the (Japanese community)
members.
It helped me a lot.

------

shoutarou さん

ご確認ありがとうございます。
ATOK 2016 をご利用とのことで、承知しました。

確認したところ、ATOK 2016 は2019年にサポートが切れているようでした。
https://support.justsystems.com/jp/list/

ですので、今回は対応しないという判断になる可能性が高そうです。

最新版の ATOK に移行しないのであれば、おっしゃっている通り、今後は MS-IME など他の IME に移行するのが良さそうですね。

-----

Translation:

Hi shoutarou,

Thank you for the confirmation.
I understand you use ATOK 2016.

I found ATOK 2016 reached EOL in 2019.
https://support.justsystems.com/jp/list/

Therefore, I think the Krita developers will not fix this issue.

If you don't migrate to the latest ATOK, I recommend migrating to other IMEs,
such as MS-IME, as you mentioned.

-----

To Krita developers:

As I mentioned above, this issue happens with a paid Japanese IME ATOK 2016,
and it has already reached EOL.
Therefore, I think this issue can be marked as RESOLVED. How do you think?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to