The locale is used to determine additional proximity characters. This
is dependent on the dictionary language, but was passed as a function
of the layout, which is wrong and would have given bad suggestions in
multi-lingual mode.
Ideally, additional proximity characters should be inserted in the
dictionary header, but for now it's a rather simple change to get
it from the dictionary's locale instead of the proximity info locale.
Also, that allows us to remove completely the locale parameter from
proximity info, which is a much needed change.
This change has zero effect on unit tests and on regression tests.
Bug: 11230254
Change-Id: If95157155db7dccd1f00b8ba55ccb3600283f9e4
The case that was not coverted well is that
CursorAnchorInfoCompatWrapper could be instantiated
with null object. In such situations, we should
do nothing.
BUG: 17682582
Change-Id: I6625a2f0ed8c5580ed9edfe4728f342da77a8e40
This CL introduces new text reference notation !string/<resource_name>
to refer a string resource on the fly.
This notation is mainly used to represent action key labels may refer
a string in a system locale in run-time.
This notation is needed to implement Hinglish and Serbian-Latin
keyboards that need to refer its own action key labels.
Bug: 17169632
Bug: 9687668
Change-Id: I042f6bd04714e0e448cd92031730eb9fb422e6d3
With this CL, the display bounds is taken into consideration
when the location of add-to-dictionary indicator is determined.
BUG: 17578360
Change-Id: I31e458fa7bbc33e539578b331fe1c51ff7f8668e
Record the horizontal and vertical gap for the key, adding
corresponding accessors. This info is helpful in interpreting
corresponding touch points data.
Bug: 17400259
Change-Id: I825c537a48db35baab71580ff5c41cd911094a4b
With this CL, the previously used commit indicator was reverted.
Instead we use the add-to-dictionary indicator only at the moment.
This CL also fixes the indicator position in bidi context.
BUG: 17335734
Change-Id: I5f7cf173ddc30876e2b01320acaff8ba4265edf6
Change [3/3]
Added tests for Qwerty/en-US/split
Parse the switch-case statement from KeyboardBuilder to use the right layout.
Bug: 4968173
Change-Id: If4d6d71d5900525290268d8affa55dccf1ebd4f2
Change [1/3]
This'll be used in conjunction with a user preference to split the keyboard when possible.
Bug: 4968173
Change-Id: I7a05948d67b94a55024790115ae261d7fef7941a
This CL allows to emulate the behavior of CursorAnchorInfo
in the full-screen mode to work around the limitation of
the framework.
Basically this CL copies relevant code from the framework
to LatinIME. This is actually a code duplicate which isn't
great, but probably the only way that is available right now.
Change-Id: I30bc8c3387c91c8e47252ba699cbd967d8927dad
This is a follow up CL for Ic8c6fab58c01206872a34e7ee604cdda.
No behavior change is intended in this CL.
BUG: 17365414
BUG: 17335734
Change-Id: I4299536d0cb0c660b7b564653c72c9cb409a7aa5