The NPE happens when the keyboard doesn't specify any punctuation suggestions.

Bug 18047927.

Change-Id: I9f8aa35df4f163b527dc6580a99afc6da45a96b8

Change-Id: I24cbe94f128f54fb9bfeeef78cf271fee2216c8e

Pass dictionaryFacilitator to StatsUtilsManager from
LatinIME
Bug:16553957

Change-Id: I912a0b447e5684909ff67e3653a4bd8649cd03c5

Change corresponding to ag/605384

Bug:16553957

Change-Id: I77024957b9497c45296bbbb24ca972b26348a8c3

Attempt to use dictionary facilitor without invoking
preference manager. Instead use account from settings only when
things are being reset/changed. Discussion forked from ag/591663

Overall, the idea here is to maintain an account information
inside dictionary groups. Reset the dictionary groups if
account changes (the way we do for locale). Since only user
history dictionary is currently affected, the check to reset user
history dictionary also includes the check to verify the account.
For other things remain the same.

SettingsValues holds the current account (and is updated if prefs change
due to change in account settings). The updated settings are then
propagated to dictionary facilitator via LatinIME#loadSettings.

Bug:18104749,18469539
Change-Id: I553e776e7ea125d0fb7a1fe70a4c7eb0b2277fb8

Change-Id: I40afeb4557c3b1ad32bd90f67502a625df2bc3fb

Change-Id: Ic4def69a9f742f13c98bc3e518c406658b52797d

Bug: 18705799
Change-Id: I73730ccf59e2697acfb3fe436c01b94c40307f2f

Change-Id: I546f3b1943999a41803222bd14f9ddd23aa87a51

Change-Id: I7bd71f1d4ef0fc0fe21ddfd9f3e11463f53ac4e7

For now, it is a debug preference, but we may make this a proper
user setting in the future. Thus note that the messaging is not
final.

Pref looks like :
1. https://screenshot.googleplex.com/OLxW0myWD9.png
2. https://screenshot.googleplex.com/YeqWYXGstw.png

Bug: 18106936
Change-Id: I88bbc1a2ee0c23a48ff3972a91d57c218b10bb65

Bug: 7677193
Change-Id: I66eddbf27a9db8682c0347a1be19922792a3bea7

This reverts commit 8584db14.

Bug: 18675223
Bug: 18675476
Change-Id: I4e25d87ac261c44b1943df832115f8cca690103a

Change-Id: If95c34c9eab09cbc941bef5ee3d34b9048bf3bf9

Keyboard location and location can now be set in the debug options
section.

Change-Id: I87c5a1d679489e12dccf26632c399af28087629e

Bug: 18528171
Change-Id: I6e12c006bd9eff15f3fa9cfd335bdd9fa081be61

Change-Id: I43a56beba0cf0fdf5f93c5c764edbd279ee033b2

Change-Id: I1151dc1d5db3986a97daf68c1e387dbc2e4610dc

Change-Id: I5661a7926cf5a404788516c542b25cc0707bb417

Change-Id: I7ea289f7e78aa33562c7737e91024a25c02333b6

Change-Id: I256d1c6bf96c07b10d2d063d7935e20e0ab8ea17

Change-Id: I68d2c85139e01684d5f0705f621ba223fc5e4425

Add API to ExpandableBinaryDictionary to dump content
from a given dictionary. We use this for dumping data
for sync process.

Refactored UserHistoryDictionaryTests to scrap out the util
methods for testing. These utility methods would be used
for testing sync + user dictionary code in LatinIMEGoogleTests

Bug:18106539
Change-Id: I357f9192ea1bd69a526d0b620c25616a2e8e9d5b

When there isn't a close word in another language of the
current multi-language set, we allow whitelist entries
to take force even if we are not confident in the current
language.

Bug: 18063142
Bug: 18130489
Bug: 18132240
Bug: 18136721
Bug: 18200415
Change-Id: I044674ba7b70aa86ab2a48d2e4d53a1c8007b62c

With this the most obvious problem is fixed. However there
are two remaining items : we should still enforce whitelist
when there are no close candidates at all, and we should
start in confident mode when pressing the globe key.

Bug: 18063142
Bug: 18130489
Bug: 18132240
Bug: 18136721
Bug: 18200415
Change-Id: Ibc0571ae35fc28f8d13760aa86b25db1163d3e31

Bug: 18063142
Bug: 18130489
Bug: 18132240
Bug: 18136721
Bug: 18200415
Change-Id: Ica09d11cb95308dd014c4e4e0d99a30dd66bfea9

Change-Id: I666308ada968ee7993235ad98b92f2ad522af122

Cherry-picked 6fc92899d82f4d3cb30f7bb2c57133154f0babd2 from
ub-latinimegoogle-edamame-mr1-release.

Bug: 18418991
Change-Id: Id4dff41ba488635ff9af899be6d4f84ab00a96c8

Change-Id: Ib34931836a617d0dc049fb3c9ae6686374ec8c12

Change-Id: I82d574c67b25239510f3ecc8882efe46e40677eb

...when applicable of course. This will allow for informing the
language switching authorities that the typed word was a
specific language, instead of leaving them in the dark.

Bug: 18063142
Bug: 18130489
Bug: 18132240
Bug: 18136721
Bug: 18200415
Change-Id: Ice3e7026a68c3018f54d730ec84f6762bf55899b

Change-Id: Ie5ab5cc716ef1211eb9ad76baa0467455e1f1a71

That allows to carry the language information in an
accurate manner.

Bug: 18063142
Change-Id: I0bca8981372ae10648274095b18b26a3686b762b

Bug: 18451316
Change-Id: Ia20bf388471f84c963354df050182e722d966a02

Bug: 18181427
Change-Id: Ib4dd62037b1f7b2d10496ee3e45b4a138e29f90a

Change-Id: Ic5cb55e24a2d843027ccc4e8e5d6954f9391c125

...and fix a bug that happened because of it.

Bug: 18417740
Change-Id: I7a33780adcb8f4e2625abcd3eec906dfee1f5dcf

Change-Id: Ied821df01e032ebc913d2f15dffdf41a51372ea4

Also added toString for AssetFileAddress for easier debugging.

Change-Id: Ie5d15d12bae46c31b28d8c67002e627f4c6690e3

UserHistoryDictionary currently uses locale to determine the
UserHistoryDictionary on the filesystem. With this change we
use the account name as well. Thus each UserHistoryDictionary
would following the following spec:

UserHistoryDictionary.<locale>.<account>.dict.
In case no account is selected, we default to the existing
spec:
UserHistoryDictionary.<locale>.dict

Example
UserHistoryDictionary.en_US.testaccount@example.com.dict

Bug: 18104749
Change-Id: Iab031e166b55cf2ded68275a7e9be22475737b37