More suggestions based on version 1.0.1 of the CJK plugin
Maintainers usually reply within 1 day
@LeanBitLab is already working on this.
Since Nov 1, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
The issue names no files or tests; start by locating the CJK plugin's symbol interface and the keyboard's key-input handling, then compare their current behavior with the suggestions. Clarify which symbol replacements and paired punctuation are wanted, and whether sliding up should replace long-press or supplement it. Done means the agreed symbols, automatic closing marks, and slide-up input behavior work as specified.
Written by the indexing model from the issue text.
Description
I installed and tested the functionality of version 1.0.1 of the CJK plugin, and there has been some improvement on the issues mentioned before.
However, in the symbol interface that expands from the bottom left corner of the keyboard, I think some symbols can be adjusted. For example, symbols like "#", "¥", and "&" could be replaced with symbols more commonly used in Chinese, such as book title quotation marks.
In addition, I suggest that when inputting paired punctuation marks, such as "()", after typing "(", the corresponding ")" could be automatically completed. The same goes for the book title quotation marks mentioned above.
Also, I'm not quite sure how to describe the small symbols at the top right corner of the keyboard keys. Simply put, they are symbols that can only be entered by long-pressing, but I hope they can be input directly by sliding up on the key. This can save a lot of input time because long-pressing requires holding for a while.
LeanType v4.3.0(standard);CJK v1.0.1
- Dominant language
- Kotlin
- Stars
- 1k
- Forks
- 59
- Avg merge
- 14h 9m
- Merged PRs (30d)
- 56
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LeanBitLab/LeanType
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
LeanBitLab/LeanType#766 ·
Maintainers usually reply within 1 day
-
[Bug] Silence timeout doesn't close interface and start transcription; causes silent loss of dictated speech.Possibly taken @LeanBitLab claimed this today. Openbug
LeanBitLab/LeanType#765 · 1 assignee ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
LeanBitLab/LeanType#764 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
LeanBitLab/LeanType#757 · 7 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
LeanBitLab/LeanType#753 ·
Maintainers usually reply within 1 day
All issues in LeanBitLab/LeanType
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AAswordman/Operit#1457 ·
Maintainers usually reply within 8 days
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
JetBrains/klibs-io#606 · 1 comment ·
Maintainers usually reply within 1 day
-
Python: zadd stringifies bytes/bytearray/memoryview members (silent data corruption), including in BatchPossibly taken @prateek-kumar-improving claimed this today. Openbug 🐞 python 🐍
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
valkey-io/valkey-glide#7521 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
open-telemetry/opentelemetry-android#2183 ·
Maintainers usually reply within 2 days