| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Autotext correction would check whether the first suggestion
so far was the same as what Autotext would return, and if it
was indeed the same, would not send its result as
autocorrect. However, the first suggestion is not guaranteed
to have a high enough score to trigger autocorrection, and
there would be cases where a word in autotext would not get
autocorrected because the word came out of bigram
suggestions. These occurrences would be extremely rare, as
they would require concomitant insert between autotext for
one char and bigram suggestion. It is, in fact, probably
limited to the capitalization of "I".
This did not happen in gingerbread because gingerbread would
not register 1-letter words as valid bigrams.
This fix works by just always sending the result of autotext
regardless of whether it is already the first suggestion or
not. This is okay because duplicates are removed afterwards
anyway - and this processing is absolutely necessary because
the autotext'd word may actually be somewhere else in the
suggestion, so it made really no sense checking for only the
first one.
Please note that there is also a race condition that can
result in "i" not being converted to "I": at the moment,
Latin IME relies on having the suggestions evaluated
at the time autocorrection is performed, but when typing
very, very fast, those messages may have been canceled.
This is not limited to the autocorrection of "i", but
affects all autocorrections. It requires a nearly
inhumane typing speed to trigger, but hitting "i" and
space in turn as fast as one can it's possible to
reproduce occasionally.
Bug: 5135113
Change-Id: I530ea6212487300001a2c0fc5b25a5c7716bdf63
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a followup for Ie1d69131.
Bug: 5023981
Change-Id: I42ec596af40cb7dcdd84b96ba5bff9ef1fb5dc92
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
The locale is specified by KeyboardLocale extra key in method.xml,
LatinIME will use the specified locale for keyboard layout.
Bug: 5238658
Change-Id: I8e6cb66c73a7ac1bf611d9910b42fa9cff38eba0
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: 5023981
Change-Id: Ie1d69131dbf884a3f6a2beb3ac3427e5437c1486
|
|/
|
|
| |
Change-Id: I5c57752772414b4f9475d0ad43d7fc52b97c3f33
|
|
|
|
|
|
|
|
|
| |
Move bigram suggestion option to the advanced settings screen,
remove bigram prediction option for ICS release and remove the
now-empty bigram option category.
Bug: 5240082
Change-Id: Ib1fc608ad33d5598410f7b0cb4a1639bffef28c7
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Checking the magic number of a file upon decoding is necessary,
because if the file is corrupt and we don't check it, we will
fall back to a simple copy of the corrupted file. Latin IME
would realize this and would not crash, but would not use the
corrupted dictionary. If this happened to be a main dictionary,
then the user would lose the ability to use the correct
built-in dictionary.
Not the same, but kinda similar to
Bug: 5223031
Change-Id: Ic2783dc9dd5f3dcf2865623d9452765fe3778db7
|
|/
|
|
|
| |
Bug: 5023981
Change-Id: I14ded3c3d554ac72b66f190110652f54d91df954
|
|
|
|
|
| |
Bug: 5023981
Change-Id: I737bacb1a6bb40f70be65d6eff85614afe6c79ed
|
|
|
|
|
|
|
|
|
| |
This fixes a race condition that would end up with the spell
checker not finding some words in the user dictionary when it
just booted.
Bug: 5194627
Change-Id: I1ba911cc53e6ae3b111d54a6f91d1d5feef3f5de
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I7e9e6e5bc4486d8618d0213b112308c3d305c15e
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I8cfad5f780a481a251cc4f752bff3cda5ae3ffbe
|
|/ /
| |
| |
| |
| |
| | |
Bug: 5219037
Change-Id: I0300fbc7e1cc97f0f8ba4d21e0e699d9fe66ed76
|
|/
|
|
|
| |
Bug: 5218662
Change-Id: I094b2ceb7438148eb5bdf620b188f598e8442a07
|
|
|
|
|
| |
Bug: 5058488
Change-Id: Ib12013f58afad957a8205b439f87480cc12ea06f
|
|
|
|
|
|
| |
...that was missing
Change-Id: Ia3b17909f295e0a93dee633c8d67c0e03840023e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The message this removes gets printed under normal conditions.
Normally dictionary files are compressed then crypted, but not
compressed a second time; however LatinIME tries to open a
compressed-crypted-compressed file first, because it could not
do it afterwards and we want to support this case. So under
normal operations, the first method LatinIME tries is actually
expected to fail.
Also, if we decide to stop compressing or/and encrypting dicts
LatinIME supports it as a valid use case. It should not print
errors to the log.
If the file cannot be open at all, then it is an unexpected
case, and Latin IME still reports to the log.
Change-Id: Ic5228c51365a101af1d03e2c893484d3050b5a1c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This change also tweaks more_suggestions_hint drawables to eliminate
unnecessarily padding at the bottom.
Bug: 5204563
Change-Id: If5ec731c9a490da0116a020e8fd405c7d025d707
|
| |
| |
| |
| |
| | |
Bug: 5095140
Change-Id: I7000f752bc9b7fd6a7af4839b2f225c085300128
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is preparation to have the decrypting/unzipping code
moved over to LatinIME.
Bug: 5095140
Change-Id: Ic3fdcc3de673b46cef2eb9ebe6a52cbdd614e50a
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I3ea8ffcdefcefaa82ae76a31bb65977009d8a040
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
This change also introduces "AsciiCapable" extra value for subtype
that indicates the subtype can input any ASCII code point from its
keyboard layout.
Only if the input field has "forceAscii" private IME option and the
current subtype doesn't have "AsciiCapable" extra value, the en_US
keyboard layout will be used for the input field.
Bug: 3384942
Change-Id: I25e2553e37ecb5002df1164e45f6273845fe463b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
LatinIME has several fallbacks to ensure a dictionary is used.
However, it should now be possible to deactivate the main dictionary
through the dictionary pack settings. In this case, Latin IME should
not fallback to the built-in dictionary.
Change-Id: Ibd992ad89793169f04a968b40781fce819b87b6f
|
|/
|
|
|
| |
Bug: 5182291
Change-Id: I5089a14902b9f4ff1ab4f34e3f7a42aca5040d3e
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 5182291
Change-Id: I6a88ed4df3ec98e31ea4966d82da56f7fca342ac
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: 4311428
Change-Id: Ie7e094ded9c7c1fe811b7eb97bc33ffecb29a73c
|
|/
|
|
|
|
|
|
| |
This also adds some optional debug code to detect more easily possible
future occurrences of the same problem.
Bug: 5195017
Change-Id: I2558b468e46f7090de868f1ec2dc9e24895d670f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This change also shows the valid typed word in bold face.
Bug: 5161713
Change-Id: I15355a11888fc8ef90ecc8b64a52eb08c1a2b367
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Bug: 5175740
Change-Id: I592401b3b8c3074d70e06dc3a9919cc3cb47ba49
|
|/
|
|
|
| |
Bug: 4311428
Change-Id: Ic93f264101d13963503fcd447a69bbffd06e69f3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new behavior is as follows:
- If the word in the dictionary is not fully lower case, then the
exact case is required to match.
- If the word in the dictionary is fully lower case, then any of
the following patterns match:
- fully lower case
- only the first char capitalized
- all caps
Any other capitalization is rejected.
This is probably what people want. If you type a name in all lower
case, it should be marked as a typo, but if you type a word with a
capital for emphasis or just because it's the start of the sentence,
it should match a lower case word in the dictionary. If you have
a spurious capital letter in the middle of a word because of a typo,
it should be marked as such.
Accents are not affected, and should not be. An accented letter
is a different letter and a missing accent should be reported.
We should maybe consider again for some common transpositions
like the "ue" digraph for German, which is now considered a typo,
but will suggest the correct diacritics as the first suggestion.
Bug: 5145751
Change-Id: I651e24f13c90fb94700a1674ad380e95336e7dca
|
|
|
|
|
|
|
| |
by ignoring its preference value, when the "show settings key option" in
the settings is disabled.
Change-Id: I934be2d9eb0bf6bf731e03f5d9b752de4a7a1c7c
|
|
|
|
|
|
| |
This is preparation for bug: 5175740
Change-Id: I18b2042317f740cb1e021d3dfbf90ecfbb1a1d37
|
|
|
|
|
| |
Bug: 5175868
Change-Id: I165eee4c865caa5ee1daf3e0b1acde8788b996ef
|
|
|
|
|
| |
Bug: 5095140
Change-Id: I02032923ca2a65bd8fbabc0abbe6a476f7542187
|
|\ |
|