Skip to content
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

Status of Project? #8

Open
kamiyaa opened this issue Jun 25, 2022 · 1 comment
Open

Status of Project? #8

kamiyaa opened this issue Jun 25, 2022 · 1 comment

Comments

@kamiyaa
Copy link

kamiyaa commented Jun 25, 2022

Would love to get an update on the status of this project because I wish for this project to succeed.

ie. Any progress/roadmap? Are there any alternatives for wayland/sway?

And also if its possible to add documentation on how to test it/play around with it.
Screenshots would also be appreciated so users can know what it looks like.

Thanks!

@xdavidwu
Copy link
Owner

This works for my daily workflow. There are some more planned features in #1, but I personally don't need them and have no time to work on those yet. I would say that this project is not done, but already in a shape good enough.

As for alternatives, there is wlpinyin, which uses RIME engine instead and should also be capable of inputing traditional chinese with even more input methods. But note that wlpinyin, instead of a candidate panel, they use preedit buffer to show candidates in a text-based inline style. I have heared that there are also efforts in fcitx5 on making it wayland-native with input-method-unstable-v2.

There is also some alternatives that are not wayland-native but kind of works, like fcitx4 via its specific GTK IM module. With fcitx4, candidate panel will still be presented with X11 (via XWayland), and last time I checked XWayland still have no proper HiDPI support. Note that this set up will also encounter issues with candidate panel position.

About how to use these wayland-native input methods (those using input-method-unstable-v2, including wlchewing, wlpinyin and others), in general, make sure that you have environment variable GTK_IM_MODULE set to wayland, and you should be good to go. But note that last time I checked, there is still no client support of related protocol (text-input-unstable-v3) in Qt, and thus Qt apps won't work with these input methods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants