[webkit-qt] Spellchecking with C API (was: APIs going forward)

Kenneth Rohde Christiansen kenneth.christiansen at gmail.com
Tue Feb 5 02:21:32 PST 2013

Isnt that the exact reason why there is a WK C API for replacing the
default spell checker?


On Tue, Feb 5, 2013 at 11:17 AM, José Dapena Paz <jdapena at igalia.com> wrote:
> El mar, 05-02-2013 a las 11:00 +0100, Kenneth Rohde Christiansen
> escribió:
>> Why use enchant and not just use Hunspell (like Firefox, Chrome,
>> Opera, Mac, Openoffice). That also allows for using the Chrome version
>> which uses binary dicts and provides faster start up time and lookups.
> Point of using enchant is that it is pluggable, and allows to add other
> text checkers. This is a requirement here, as we'd be using an internal
> spellchecker.
> In the scenario of enchant, the solution would be adding a new backend
> for Chrome version of Hunspell, or make enchant Hunspell backend use the
> Google Chrome Hunspell.

Kenneth Rohde Christiansen
Senior Engineer, WebKit, Qt, EFL
Phone  +45 4294 9458 / E-mail kenneth at webkit.org


More information about the webkit-qt mailing list