When I use the Japanese IME, the input character string disappears or garbled characters occur.
Hmm, I don’t have any experience with Japanese. Can you give an example? Perhaps paste a string here, and then screenshots of how it should look, and how it looks in our app?
This screenshot will show you the weirdness of Japanese conversion. I will take a screenshot again when I can find garbled characters.
I have a related problem with Japanese Input Methods. In the title field of notes, Japanese text is partially disappeared.
When I typed “niho”, it should be shown underlined “にほ” in Hiragana. However Agenda shows only left half of “ほ”.
So is the problem more layout, ie, that things get cut off, or are the characters you enter showing up completely wrong? Ie wrong language characters?
I’ve just uploaded new screen capture about this issue.
The problem is consolidated into two points. One is that character strings are not displayed when you enter double-byte characters. The second thing is that typing a double-byte character will display it with the wrong character code.
In my case, the problem is seems to be related to layout.
I tried to debug and found
AutosizingTextField. I think that it will expand according to the length of the entered characters. However, is not it working well with Japanese uncommitted text.
So you mean it gets cut off when you have only entered part of the symbol? When you finish the symbol, does it fix itself?
The problem is very likely some transformation of the text we are making. Perhaps we are not properly handling the double glyphs somewhere.
It would probably help a lot if someone could give us a little test. Tell us exactly what to type, and how to type it, and what should be shown. I have never worked with Japanese, so will need some explicit instructions about how to enter the text to see the issue. Then I can do some tests and track it down.
Japanese is expressed using Hiragana and Kanji. In Japanese input methods, you can input Japanese text a few steps.
First, you can enter Hiragana from any alphabetic keyboard. Hiragana is a phonetic character. The letter “こ” pronounces [ko]. To enter this letter, enter “ko” with the alphabet.
If you type
korehanihongodesu., you will see
これはにほんごです。 in Hiragana.
The Hiragana string entered here has not yet been committed. That uncommitted string is shown as underlined. At this point, Japanese input methods display candidates for this uncommitted string. By selecting the suitable conversion result from the candidates, you can enter Kanji.
これはにほんごです。 will be converted to
これは日本語です。 (means “This is Japanese.”). In this example,
日本語 is Kanji.
When you select a candidate, the string is committed and the underline disappears.
So, I mean uncommitted string gets cut off. And I commit the string, it has fixed.
Thanks for the explanation, we’ll dive onto it
The same issue happens to the Chinese IME. All double-byte input seems to be affected. I also experienced predictable crashes when typing in tags in Chinese.
Thanks all for the help, one question, is the problem only in the title field or also in the main notes area?
Both title field and main notes have some problems with CJK IME, but their behaviours are different. In the title field, characters are shown right after they’re typed, as it should be, but only a narrow part of the text can be seen until a space or enter is pressed.
In the main notes area. The characters are not visible at all (until a space or enter is pressed).
Thanks a lot, I’ve just fixed the title issue, the main notes area is next, we hope to have both fixed in the next update later this week.
UPDATE: Today’s c3 update includes fixes for handling multi-byte languages such as Japanese and Chinese in the title field of the note, please let us know if the title field now behaves correctly. We will focus on correct handling in the text area next (which is not yet fixed in this update). Thanks for the feedback and your patience!
UPDATE: The new c4 update includes fixes for Chinese and Japanese in the main text editing area of notes. Please let us know if there are any remaining issues.
I think that all the problems I experienced have been fixed
Thank you so much.