Weng Xuetian

Sway current implemation seems to also a conflict between wl_keyboard.enter & text-input-v3.enter text-input-v3 focus may not follow wl_keyboard focus in this case as seen in the message trace.

Specifically, the code here: https://github.com/swaywm/sway/blob/2686afb95c5dd76b22abdd76ffbb4b30688f8fd3/sway/input/seat.c#L807 virtual keyboard is implemented as a "sway device" thus it may trigger the "synthetic" focus change here. This somehow may mess up the application that...

Seems also happen on chrome version this afternoon.

Here’s a real life example that an extension want to use appstream-compose, but have to manually execute appstream-compose in post-install. https://github.com/flathub/org.gimp.GIMP.Plugin.Resynthesizer/blob/639782fd175e1bd16b34a2327016d42355eb529e/org.gimp.GIMP.Plugin.Resynthesizer.json#L29 Also, appstream data supports the concept of addons, so...

@kchibisov right now winit uses libX11, and libX11's xim implementation is really buggy and easy to block when IME quits (e.g. libX11 code wait for XIM messages in sync fashion...

@rocka m17n is commonly used for many Indian languages

云输入在之前的讨论中主要是有个小技术问题，在桌面上网络通信是采用 curl 这个库，但是安卓上的 curl 有一些证书相关的问题（关于让 curl 使用系统的证书，否则变成需要自带一份根证书也有潜在的问题），而正好这个问题是绕不过去的，因为云拼音为了安全是都是使用 https 进行访问。 所以并不能简单的直接移植，权限的事情反而是其次

@rocka 一般来说有专利和版权两方面的问题，已经包含的五笔都是专利过期的

從 fcitx 的角度來說，問題就是 libchewing 需要提供一個完全禁用本身全形功能的開關（包括禁用 shift + space 切換功能） ，然後只需要額外增加一行代碼就可以像其他的 fcitx 輸入法那樣非常簡單的直接調用 fcitx 的全形功能了。 從 api 的角度來說 shift + space 的實際功能對 fcitx 來說是黑盒，所以我不想直接在 fcitx的 engine 代碼裡面不將 shift +space 傳給 libchewing。

Thanks. Didn't know about that, but it looks like extension are not being handled. I updated the title to make this issue tracking the support for detecting extension update. I'm...