please support Chinese

[dtguubody]

It supports so many languages just Chinese.please support it!!

[LeanBitLab]

Here is the technical reality:

UI vs. Logic: Having translation strings (e.g., "Chinese" in the settings menu) or XML subtype definitions only creates the menu item. It does not provide the logic to actually process Chinese input.

Missing Components: To support Chinese, the project needs:

• Dictionary Data: A database of Chinese characters and their Pinyin/Zhuyin/Cangjie mappings.
• Conversion Logic: An algorithm to convert Latin alphabet input (e.g., "nihao") into Chinese characters (e.g., "你好").
• Candidate Selection: A UI and logic system to let users select the correct character from a list of homophones.
• Prediction Model: A language model to predict the next character/word.

The current codebase is a basic Latin-based keyboard . Adding Chinese is not just a configuration change; it requires implementing a complex input engine or integrating an existing open-source library (like the one used in AOSP's LatinIME with added CJK modules, or a dedicated library like opencc combined with a dictionary).

[dtguubody]

all right😥

[LeanBitLab]

all right😥

ill try to find any workaround after making the keyboard become stable enough and we have enough time for the research, there might be a way, for now its just too much changes we need to do that may break the current keyboard

[marcusemular]

I wait update for Chinese 🌤️

[olivertzeng]

Here is the technical reality:

UI vs. Logic: Having translation strings (e.g., "Chinese" in the settings menu) or XML subtype definitions only creates the menu item. It does not provide the logic to actually process Chinese input.

Missing Components: To support Chinese, the project needs:

* Dictionary Data: A database of Chinese characters and their Pinyin/Zhuyin/Cangjie mappings.

* Conversion Logic: An algorithm to convert Latin alphabet input (e.g., "nihao") into Chinese characters (e.g., "你好").

* Candidate Selection: A UI and logic system to let users select the correct character from a list of homophones.

* Prediction Model: A language model to predict the next character/word.

The current codebase is a basic Latin-based keyboard . Adding Chinese is not just a configuration change; it requires implementing a complex input engine or integrating an existing open-source library (like the one used in AOSP's LatinIME with added CJK modules, or a dedicated library like opencc combined with a dictionary).

is porting something like fcitx maybe doable?

[LeanBitLab]

Here is the technical reality:

UI vs. Logic: Having translation strings (e.g., "Chinese" in the settings menu) or XML subtype definitions only creates the menu item. It does not provide the logic to actually process Chinese input.

Missing Components: To support Chinese, the project needs:

* Dictionary Data: A database of Chinese characters and their Pinyin/Zhuyin/Cangjie mappings.

* Conversion Logic: An algorithm to convert Latin alphabet input (e.g., "nihao") into Chinese characters (e.g., "你好").

* Candidate Selection: A UI and logic system to let users select the correct character from a list of homophones.

* Prediction Model: A language model to predict the next character/word.

The current codebase is a basic Latin-based keyboard . Adding Chinese is not just a configuration change; it requires implementing a complex input engine or integrating an existing open-source library (like the one used in AOSP's LatinIME with added CJK modules, or a dedicated library like opencc combined with a dictionary).

is porting something like fcitx maybe doable?

Need some proper research about it, will check it later, maybe we can create another repo or loader like the handwriting plugin so it wont effect the current app stability or app size