extending soft-keyboard with language switching support?

by Henrik » Fri, 23 Apr 2010 08:03:47 GMT

Sponsored Links
 I just got my HTC Desire with Android 2.1, and the first problem I'm
running into a lot is when using the visual keyboard.  Being
multilingual and having friends who only speak one particular
language, there's no single 'correct' input language setting for the
word prediction feature, so I started looking into how much work it
might be to extend the keyboard with two rather basic, though
essential, features:

1)  Showing the current language selection, so that I don't have to
type stuff, getting it mis-corrected, then discover the language
setting must be wrong, go into the settings, select to change
language, select language, etc... until I get back, erase the old text
and start over. That gets old real quick..

2)  Being able to simple change whatever language is used for the word
prediction by just having a button on the keyboard doing that
directly, i.e. a button that just cycles through the 'relevant'
languages with the key label showing which is currently active.

Improving it even further, one might imagine:

3)  Having a per contact setting, noting the word-prediction language
that should be used when communicating with that user.

But searching through the docs, I'm slowly coming to the realization
that the input text language setting may not even be available to be
changed outside the system settings dialog, making this impossible to
implement - is that correct?

Henrik Gram


Other Threads

1. How could I run a Uri based Intent in a Tab Page?

Sorry, no plan to support it any time soon.

On Sat, Jul 4, 2009 at 1:43 PM, Marcus Gustafsson

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.


2. Questions on applications and how applications are to follow hardware limitations?


I have a somewhat related question.

A lot of android powered phones will become available in the next
And as I see manufacturers trying hard to customize their android
versions, to make their products more appealing to the consumers.

So how can Google (and the Android team) defend the platform from
becoming fragmented ? I mean I'm pretty sure that no manufacturer can
modify the base framework in a way which makes existing apps
incompatible with it and still call it Android powered (am I right?).

But what if they extend the framework with apis that I as a developer
can use, and if I choose to use it, will I be out in the cold alone to
sell it somehow outside the Market ?

Or should I just use the base framework as it is and hope that my app
will integrate well with the changes the manufacturer made ?

Thanks for the answers.



3. post removed about problem starting emulator from command line?

4. PhoneFactory.getDefaultPhone from apps other than PhoneApp

5. How to get the source code of Google maps for android sdk 1.5

6. Populating a Spinner from another Spinner Dynamically

7. How to set the http proxy in the real device