[SHR] illume predictive keyboard is too slow
helge.hafting at hist.no
Tue Feb 3 18:28:49 CET 2009
Carsten Haitzler (The Rasterman) wrote:
> yeah. this is one reason i want toi understand how it works without ø, æ etc. -
> one day there will be a phone with a kbd.. and it wont have a version per
> language because the # of users in norway are too small to warrant a special
> production run for them - same for germany, france etc. etc. - until you have
> the sales numbers to justify that.. you need a way to either work around it by
> ignoring them - or have software correct it. so software that works eventually
> with a hw kbd and inserts the right ø, æ etc. based off normal a-z typing...
> would be useful.
If we someday get an open phone with a keyboard, then I hope they are
smart enough to make enough keys. (In my case, both the q row and the a
row needs 11 keys) No problem if the keytops are painted with an english
layout - I can paint. As long as they don't let the top row end in "p"...
Surely, when there is a kayboard anyway, a couple of extra keys won't
cost much. Not if they are on all phones, instead of only "adapted"
ones. The americans can use the extras as application hotkeys.
Another approach - let the "keyboard" be an extra touchscreen that is
wide - in the shape of a keyboard. Then we can program the kayboard like
we can today. Of course this keyboard-screen can be cheaper -
monochrome, low resolution, maybe no backlight.
> i just want to understand the constraints of the languages i don't know - and
> how they are used. it gives me insight into how to solve the problem on a wider
> picture. thanks for the info.
Glad to be of help.
More information about the community