-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Japanese text input is not rendered inline #1469
Comments
This is a good point - I noticed the same thing with Japanese input. The issue is that Textual hides the terminal cursor and uses its own "virtual" cursor. The dropdown appears at the terminal cursor's position, which is at the bottom right of the widget (since the full widget repaints from top left to bottom right). It seems some TUI apps use the terminal cursor though, so the dropdown appears in the correct position. For example, vim and mc seem fine. It'll require more research from us, but we definitely acknowledge the issue - thank you for the report! |
@darrenburns , thank you for your comment and aknowledgement! |
@darrenburns |
Came to post about this issue but it's already here thankfully. Hopefully there is a fix soon for this. Thanks for all your hard work! |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
This is merged into |
I tried to input Japanese characters on "textual" demo app, and found that Textual app doesn't render IME text / list at expected place.
When typing Japanese characters (and probably other many non-English languages also), applications are expected to render IME text and candidate word list, with the help of the OS. And the position of the text and list should be the caret position in the text input widget.
I tested this only on Mac OS (Ventura 13.0.1), but I will check the same on Windows OS later and update this report.
Please see attached screenshots.
Textual app on Terminal app (unexpected behavior)
Memo app (expected behavior)
Terminal app (expected behavior)
The text was updated successfully, but these errors were encountered: