Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • trie-js-dumping protected
  • hitbox-boosting protected
  • model-metadata protected
  • lm-2-finetuning-whisperggml protected
  • lm-2-finetuning protected
  • lm-2 protected
  • language_model_experiments protected
  • 0.1.24.2 protected
  • 0.1.24.2-rc1 protected
  • 0.1.24.1 protected
  • 0.1.24.1-rc1 protected
  • 0.1.24 protected
  • 0.1.24-rc1 protected
  • 0.1.23.2 protected
  • 0.1.23.1 protected
  • 0.1.23 protected
  • 0.1.22 protected
  • 0.1.21 protected
  • 0.1.20 protected
  • 0.1.19 protected
  • 0.1.18 protected
  • 0.1.17 protected
  • 0.1.16 protected
  • 0.1.15 protected
  • 0.1.14.1 protected
  • 0.1.14 protected
  • 0.1.13 protected
28 results
Search by author
  • Any Author
  • Aleksandras Kostarevas Aleksandras Kostarevas alex
  • Dean Dean dean
  • Tom Folbrecht Tom Folbrecht tom
  • sameer sameer sameer
4 authors
  1. Mar 16, 2011
    • Tadashi G. Takaoka's avatar
      Add Utils.equalsIgnoreCase methods · e7a2512a
      Tadashi G. Takaoka authored 
      This change also corrects usage of "frequency", "priority" and "score"
* Frequency is the relative probability in dictionary.
* Score is the relative probability in suggestions.
* Priority is kind a sorted score.

Change-Id: Iafb135a4ecdb401cc505014a07c74dfcac44d699
      e7a2512a
    • Jean Chalard's avatar
      Avoid the removal of high-ranking exactly typed candidates. · d631651b
      Jean Chalard authored 
      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
      d631651b
  3. Mar 08, 2011
  5. Mar 05, 2011
    • satok's avatar
      Add the suggestion algorithm of words with space proximity · 817e517e
      satok authored 
      Bug: 3311719

Change-Id: Ide12a4a6280103c092fa0f563dd5b9e3f7f5c89b
      817e517e
    • Jean Chalard's avatar
      Demote skipped characters matched words with respect to length. · 07a8406b
      Jean Chalard authored 
      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
      07a8406b
    • Ken Wakasa's avatar
      Fix a NPE caused by a null typedWord · baf263ca
      Ken Wakasa authored 
      bug: 3514797
Change-Id: Ie1056745ded1f848d1e4f70c5344d6969de509b0
      baf263ca
  7. Mar 04, 2011
  9. Mar 03, 2011
  11. Mar 02, 2011
  13. Mar 01, 2011
  15. Feb 28, 2011
  17. Feb 25, 2011
  19. Feb 24, 2011
  21. Feb 23, 2011
  23. Feb 22, 2011
    • Jean Chalard's avatar
      Force autocorrection of matching words with different accents. · a5d58497
      Jean Chalard authored 
      When entering a word without accents the user expects the system to
add accents automatically if there is no other matching word. This
patch ensures the accented version is promoted accordingly and
autocorrection really takes place.

Issue: 3400015

Change-Id: I8cd3db5bf131ec6844b26abecc1ecbd1d6269df4
      a5d58497
  25. Feb 20, 2011
  27. Feb 18, 2011