More suggestions based on version 1.0.1 of the CJK plugin

Open
#754 1 comment 0 reactions 1 assignee View on GitHub

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
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

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

enhancement

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LeanBitLab/LeanType

All issues in LeanBitLab/LeanType

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.