commit | e1fc4f6c3c7d573f013b707ee962d58f9fb636dd | [log] [tgz] |
---|---|---|
author | Gilles Debunne <debunne@google.com> | Mon Oct 03 17:01:19 2011 -0700 |
committer | Gilles Debunne <debunne@google.com> | Mon Oct 03 17:03:57 2011 -0700 |
tree | 6615933bcd22dd7ff5915bc9d7a14cb5fe0530c0 | |
parent | f00b4decc3f0b0ebd88b9a2cdb6df959704dfd46 [diff] |
Optimisations and bugs in SpellChecker A bug was introduced in a recent refactoring: correct words didn't have their SpellCheckSpan removed, leaving a lot of useless spans. SPAN_EXCLUSIVE_EXCLUSIVE should never have a 0-length. With Japanese characters wordStart could be equal to wordEnd when parsing the text: skip these. Using toString().substring(...) instead of subSequence(...).toString() which is more efficient. Change-Id: I670870a34565939b676400091f4852152a7f7124