This change introduces new keyboard mode "webEmail" to honor
InputType.TYPE_TEXT_VARIATION_WEB_EMAIL_ADDRESS. In this mode, both
'@' key and TAB key appear on the keyboard.
The keyboard layouts will be modified with other change.
Bug: 4490948
Change-Id: I66f9bda4907da448db097e9c900199dfa700b16a
Because the holo theme drawables have "holo" effect around 9-patch as
fixed size image, so we need dedicated drawables for each sw600dp-mdpi
and sw768dp-mdpi resolutions for visual designers.
* drawable-mdpi (fallback resources)
* drawable-sw600dp-mdpi (7" tablet, phone style keyboard, placeholder for now)
* drawable-sw768dp-mdpi (10" tablet, tablet style keybaord)
Note that:
* Eventually sw600dp drawables will be updated by designers.
* We need sw768dp drawable copies because, without these, 10" tablet
will use updated sw600dp drawables wrongly.
* We have to keep drawable-mdpi as final fallback resources.
Bug: 4436327
Change-Id: I93db87ee99c2abb8d18e869e5411e3cb5bec1020
This change renames resources along with new naming scheme.
* large to sw600dp (7" tablet uses phone keyboard layout)
* xlarge to sw768dp (10" tablet)
Bug: 4436327
Change-Id: I96678fa699d2abcb48022d8878557f1486e839aa
This change also syncs the drawables with Master.
Cherry-pick: I2573786aac5fd8d543cf12d24c951b67c7353fd7
Bug: 4436327
Change-Id: I88dc0162033a1017040205590c0c34a5111b835a
This change considers that the point is on the key while sorting in
proximity key detection.
This change is the cherry-pick of I3ee91367.
Bug: 4353949
Change-Id: I04fa0acf4d32c18bea9640b39a5c770466a37803
It used to be the case that the scoring system turns up the same word
that was entered with a different capitalization, but with a lower
score than some other, more frequent word. To cope with this, there
was code that would order such candidates in the first slot no matter
what. This processing is now useless because fully matching words now
have a huge boost that ensures they will get to the top of the list,
before any non-fully matching word (which means, differing only by
capitalization or accents).
The bug that did happen with this was, if a fully-matching word got
matched by several processing passes, and the (chronologically) later
score affected to this word was weaker, it would result in the
duplicate removal pass removing the stronger score. This in turn would
mess with autocorrect.
In an effort to keep the risk at a minimum for MR1, this change does
not actually remove the useless code, but adds a check in the odd case
to avoid the bad situation. Another change will remove the code for
ICS release.
bug: 4100269
Change-Id: I18c0575332981ffec0e257e26a360995838d521e
Words that matched user input with skipped characters used to be demoted
in BinaryDictionary by a constant factor and not at all in those dictionaries
implemented in java code. To represent the fact that the impact of a skipped
character gets larger as the word is shorter, this change will implement a
demotion that gets larger as the typed word is shorter. The demotion rate
is (n - 2) / (n - 1) where n is the length of the typed word for n >= 2.
It implements it for both BinaryDictionary and java dictionaries.
Bug: 3340731
Change-Id: I3a18be80a9708981d56a950dc25fe08f018b5b89
For German : handle "ae", "oe" and "ue" to be alternate forms for
umlaut-bearing versions of "a", "o" and "u".
Issue: 3275926
Change-Id: I056c707cdacc464ceab63be56c016c7f8439196c
