[BUG] Hashtag auto-completion interferes with e.g. Chinese input method
In The Archive, Chinese typing requires pressing the space key, and there will be an underline before pressing the space key. However, the automatic completion starts before pressing the space key, which leads to the inability to use Chinese in automatic completion.
The auto-completion feature should exclude text with underscores. because when entering Chinese, it is all some underscored letters before confirmation.
As shown, The auto-complete feature swallowed the first letter "n".
Post edited by ctietze on
Howdy, Stranger!
Comments
Ah, I tested this wrong. I have Pinyin setup. But I can only somewhat blindly go through the motions and see where I land
I cannot make any sense from the picture of the actual output here. Like, is that suggestion that's left over still related to "ni", or "hc" input?
Could you send a brief list of input steps to reproduce, and tell what should happen instead?
#
? (Above, it looks like "ni", space, "hc".)Author at Zettelkasten.de • https://christiantietze.de/
#你好
In the pinyin input method, pressing "nihao" on the keyboard followed by the space bar allows you to input the word "你好".
However, after enabling the auto-complete feature, pressing "nihao" on the keyboard after entering # does not result in "你好". In short, after entering #, it is not possible to input Chinese normally unless the auto-complete feature is turned off.
Same issue here. It seems that the auto-completion only works for the English or other languages that use the Latin alphabet directly (e.g. German, French).
When I type #你好 [The key sequence is 'nihao'.], the tags list won't pop up and the tag will become '#n i好' or '#ni好', which doesn't mean anything. The same problem occurs in Korean input. The auto-completion may recognize the letter as English. However, when I use English, everything works fine.
By asking ChatGPT, after setting the input method to "Do not display any pinyin letters in the edit box", But the issue still exists in The Archive. However, the same issue that previously existed in the Keyboard Maestro search box has disappeared.
Thanks for the explanation! I'll investigate how the character input list and the auto-completion popover interfere
Author at Zettelkasten.de • https://christiantietze.de/