Bug 39580 - extend the keyboard possibility
Summary: extend the keyboard possibility
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-20 18:48 UTC by Js Lebacq
Modified: 2020-09-30 04:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Js Lebacq 2002-03-20 18:34:49 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kde
Version:           KDE 2.2.2 
Severity:          wishlist
Installed from:    RedHat RPMs
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
OS:                Linux
OS/Compiler notes: Not Specified

Hello

the input area is an important one. Currently it is difficult to obtain for example the mathematicals symbols when you type an unicode text. For real use
I think all characters must be accessible thanks a keyboard manipulation.

So I wish KDE offer a texmacs-like input method (perhaps it's also an emacs input method but I'm not an emacs user). Imagine that configuration :
- if you type "a" you simply obtain "a" on the screen
- if you type "<" the final symbol is function of the the key wich you type then. For example "<=" key-combination gives "\leq" symbol (I use the latex
language) "<a" key-combination simply gives "<a" because "<a" has no special mean and "< " (a "<" and a space) gives "<" because space is an echap symbol (useful if want to simply type "<<").

In texmacs you can see the key-combination wich you type in the status bar of that application but we can imagine an applet of kicker or an another better GUI method sothat user can visually control what he do.

To be very useful the set of key-combinations must be function of the "context". Examples :
- if I type a text coded with ISO-8859-15 the "oe" key-combination could give the o-e ligature
- if I type a text coded with ISO-8859-3. The o-e ligature doesn't exist so the "oe" key-combination could be free for an other use and the "^g" could give that special character useful for typing esperanto wich is a "g" with a circumflex accent (useful if you don't want to use dead keys).
- if I use kformula...

Moreover the result of a key-combination could be an other things than a character but could be a special thing which have mean only for a particular
application (think kformula too).

I realize it's an heavy piece of coding but such an input system is very very useful : I already imagine the way I could use it in a lot of KDE apps.

Regards Jean-Sébastien Lebacq.

(Submitted via bugs.kde.org)
Comment 1 Martin Koller 2006-11-18 12:03:38 UTC
As this usage really depends on the application you are working with, why not simply using kcharselect ?
Comment 2 FiNeX 2008-05-05 15:09:51 UTC
Maybe on KDE4 it could be implemented a plasmoid which integrate kcharselect :-)
Comment 3 Nate Graham 2020-09-30 04:36:29 UTC
KCharselect already does this and there's a KRunner runner you can download I believe.