I can not enter 2-byte characters properly on iOS Devices. The behavior differs depending on the input application(IME). When the user wants to convert input into Chinese(kanji) characters and confirm character input: - User do not convert, IME(by apple) can be input characters if raw input. - When the user performs Chinese characters (Kanji) conversion, only the first character is input. (Third party IME). In Calc, there is a different behavior. Direct input to a cell behaves the same as any other. However, if user select a cell and enter in the upper formula bar, user can enter without problems. In the input mode, the entire Web page is enlarged twice and displayed. *This is a different problem. The problem of Chinese characters(kanji) input related to the desktop occurred simultaneously with the following. https://bugs.documentfoundation.org/show_bug.cgi?id=122329 This issue has been resolved in Collabora Office 6.0-29.
Confirmed. This is probably close to predictive input not working on mobile devices in general, see bug 94087.
*** Bug 127095 has been marked as a duplicate of this bug. ***
Collabora Office 6.0-29 (git hash: 9812eeb) This version finally made it impossible to input Japanese (2-byte character)by iPhone. Writer was completely impossible in the previous version. In Calc, Japanese can be entered by typing in the formula bar. However, the display of Calc is confused. If I change iPhone device vertically and horizontally, it will return to normal. Writer is easy to understand. I try to input Japanese on iOS/iPadOS. Unlike 1-byte character input, 2-byte character input has an input candidate selection process before registering characters. In the current Collabora, the "backspace" function seems to work when the input candidate is determined. When I input a 2-byte character, the character is not registered in Writer, and the cursor is moved to the end of the already registered character. For double-byte users, this is a fatal problem.
Thanks for retesting the issue with the latest version. Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.