<div>Hi,</div><div><br></div><div>Multiple ports can share the implementation if we put spell checker in WebCore. Ports without native spell checker can use Hunspell based spell checker without much efforts. Brew MP port is also interested because it does not have a native spell checker.</div>
<div><br></div><div>Regards,</div><div>Kwang Yul Seo</div><div><br></div><div><br></div><div><div class="gmail_quote">On Thu, Nov 18, 2010 at 5:27 AM, Brent Fulgham <span dir="ltr"><<a href="mailto:bfulgham@gmail.com">bfulgham@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">>> On Wednesday 17 November 2010 04:52:36 Hajime Morita wrote:<br>
>>> Hi WebKit folks,<br>
>>><br>
>>> I'm thinking about porting Hunspell-based spellchecking code<br>
>>> from Chromium to WebKit/WebCore.<br>
<br>
</div>At least in the Windows implementation (WebKit/WebKit source base),<br>
the spell checker is implemented on the client side as a delegate<br>
operation.<br>
<br>
I wrote up a few notes on the topic<br>
(<a href="http://whtconstruct.blogspot.com/2010/07/spelling.html" target="_blank">http://whtconstruct.blogspot.com/2010/07/spelling.html</a>).<br>
<br>
What would be the advantage in placing the spell checker in WebCore,<br>
as opposed to the relatively agnostic approach used via the WebKit<br>
API? Is there a performance benefit, or a means of hooking into some<br>
other part of the system not currently served by the existing spelling<br>
infrastructure?<br>
<font color="#888888"><br>
-Brent<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev" target="_blank">http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev</a><br>
</div></div></blockquote></div><br></div>