The new constructor is used for creating dictionary instance
that uses a given file.

Bug: 11956652
Change-Id: Ifbf420a1a768eb95a5c3a58eeb1be5936b306d35

Bug: 10667710
Change-Id: I7a189e32286a6005393fbde8da736541ca9226a8

This simplifies the code quite a bit.
- GERMAN_UMLAUTS are now handled through a key-value attribute.
  The dictionary generator does not need to know about it any more.
- FRENCH_LIGATURES are deprecated as we handle them with shortcuts now.
- CONTAINS_BIGRAMS is deprecated. Bigram processing is always applied
  regardless of this flag.

Bug: 11281748
Change-Id: I55a11ba61d3589c1584a3fa6c941374b349b7b5c

Bug: 12089197
Change-Id: Ia898f8d2836c0c131a1834dc0a396d9121ecb972

Change-Id: I2a89497fb9ec12a37ba09f4598742e88f6700576

Bug: 12025402

Change-Id: Ia0bb13b2e26aa60a67dff73f3f6a1e276f1bb1dd

Change-Id: If7497310485a895dd22b8df29dc13508acaa0ab6

cf. Ibe392f5f9dbc82c3cdff8e06b958bc3bcce3fa82

Also, cf. bug id 11340849

Change-Id: I43e84f8ca04eb1aa74037a705970a36434429a0f

One of these cost me a day and a half searching for a bug :(

Change-Id: I20f0b727f7c02e2754aaaf6a05b74c9cf9e6375e

Bug: 11281748
Change-Id: Ia2490d18bf159990310e10ed45fb6b3a0dee1c5f

Now, PersonalizationPredictionDictionary can be used not only
for prediction but also for suggestions.
We should rename PersonalizationPredictionDictionary to
PersonalizationDictionary.

Change-Id: Ifcf4459072f3523e3f3dc783f12e15b89cdbb12d

Bug: 11736529
Change-Id: I62a7469afe03092ec992bfb190f717223a8c556f

Bug: 11956652

Change-Id: I59f1823bbc0146f6d2f34cbed8166bb6de197208

And fix a couple bugs.

Bug: 11281748
Change-Id: If07953a4b1ff9eb1165af03fdb332d7e47cd8f32

Make the version number a single number on native and java side.
Also, remove the hasValidContents method. It's useless since the
native code already checks this when creating the dictionary (I
wish I had known that when I added it).

Bug: 11281748
Change-Id: I572d37429972b2f280e4bdb748b709e5d0d7737e

Bug: 11281748
Change-Id: Iff45fdf6b23f77c08271a169c7d7ca45912c85e8

This implements the skeleton implementation, and enables a
fallback implementation in the case the file is coming from the
dictionary provider.
- A better scheme should be used for provider-supplied dicts.
- This does not implement the solution for device-generated
    dicts yet. This will come in a future change.
- This does not implement the checking process on the native
    side yet. This will come in a future change.

Bug: 11281748
Change-Id: Ifa6e237d19dfbffe503e3674915480ea867b0ddf

Bug: 11073222
Change-Id: I77c99fbea2f255dbfddb646b6e12bee574647eca

Bug: 11073222
Change-Id: I232d41bec5df7952856b5ba4765977707c39b94a

Bug: 11073222
Change-Id: I89e1277f734d5959e33d61e7e9e7048084b9007a

Bug: 11973488

Change-Id: I91ef720a24633aec0f4e81cd4f7c49c749805c49

Add a warning comment and make it so that openNative()
is only called in one place in the code.

Bug: 11281748
Change-Id: Ic7819a01deb62cf145ebf9d620da2d15fae19313

Change-Id: Ia16880e818927bc3df7292e130b2f7b5efc9776e

Change-Id: I10c29bd45fd37d765f115333087e1700dd90570b

Bug: 11960453
Bug: 11954718
Change-Id: I71e98cc6ab30cc89e921e9ef578d7f6366049d01

Change-Id: Iddde1f85139cb21bde6e4fc275c32f3d62f4862f

This had to be a typo

Change-Id: Id49e44d7667d64b00e883c55c683535398b6bdea

Change-Id: I6fb11b8cb52c06b805fb17d61450d7df50e4e20d

Change-Id: I0f2b408b4976d8119c932654e23836803d42c568

This fixes a few bugs that became apparent with the
reinstating of a test.

Bug: 11954718
Change-Id: I1127bc3180f856566429f40d14c944e6f0007e09

Bug: 11956240
Change-Id: I3de1ebbf96fa2422124e4d8e50190adfa09b8a49

Bug: 11073222
Change-Id: I76e47d0399cf43fc3cc18cb1252f166be86b9a69

Change-Id: I024f0ee9c7f7718afc8a4ca0c6c49f2e88b035ad

Bug: 11073222
Change-Id: Iabae12b8f14a9da3cdc804dcc6af443cedeb3f99

Bug: 11328842
Change-Id: I08229e895fc34403932648b9b931583d965f0e01

Change-Id: I86d3162a90e0068e787a906c0d3d64102487620a

This should take into accounts word connectors.

Change-Id: Ic7fa5c837cd65a43ba43d7ae9d299b8d20019892

Bug: 11883501
Change-Id: Ie3f496935f9600e2bde51cbebed2b4f8c90c25b2

They are not failing because of this right now, but future
tests would fail without this.
Concretely, since the Handler for any given main thread is
a singleton managed by the framework, the messages won't
be removed automatically. In particular, messages posted
with a delay have a large destructive potential, because
they will go through before the startInputViewInternal
method is called, because it's called with a message too (in
turn, this is because of working around framework bugs).

Bug: 11142685
Change-Id: If81a168efcfd7d93806ddc4ea432d438c45a3e1d

Change-Id: I3a1b06fa028dbf130c7aa2c83e9ec1a180aa1f5c