Text input is the foundational means of human-computer interaction: We configure or systems, program them, and express ourselves through them by writing text. It's how our software is made, and it's how it's consumed. It's how users and developers connect with each other.
Yet text input in our software is not complete, and it's not as strong as it could be. Some cannot use our software to write text at all. Others are not doing it as efficiently as they could be, or with as much joy.
The good news is that improving this is within our reach. If we care to do so.
I propose that we spend time and effort on:
- ... enabling more users to write their language in our software
- ... allowing all of our users to input text with greater efficiency
- ... bringing more joy to text input by improving support for emoji
- ... making text input act consistently across different input devices
- ... addressing key defects in our software related to global text
To do this we will:
- Improve support for Input Methods in Plasma by making it always-on and redesigning System Settings and runtime UI
- Improve support for emoji with an easily accessible emoji input palette
- Improve the convergent text input experience by making physical and virtual keyboards act consistently
- Improve global text support in our application software by fixing key bugs and adding missing features
What it will take
UX designers, artists, translators, shell programmers, library programmers and application programmers will need to organize and assign work items, document new knowledge and create checklists, and implement the proposed solutions across all of our software.
How we know we succeeded
We'll have succeeded when our systems and applications can be configured to write and display the world's most prominent languages and writing systems (including emoji) easily and efficiently. The result will make free systems viable for more users across the globe and expand our community.
I am willing to put work into this
- Eike Hein
I am interested
- Nate Graham