Le 8 août 10 à 23:49, Abdelrazak Younes a écrit :
The first solution is to make Paragraph send strings directly to the spellchecker. This would require to rework the spellcheck interface to allow to pass full strings. I do not think that aspell or enchant allow this, although I could not find a documentation for enchant :(

The interface can be changed to pass words, sentences or paragraph. Then the implementation will tell the Paragraph which method to use.

Yes.

While I am writing this I am thinking that maybe there are (again!) some metrics and painting bugs that cause full redraw instead of single row redraw in Mac? That would explain in part the additional slowness while writing.

Note that aspell is reasonable fast on the Mac. Of course, gaining a factor 2 or 3 on the slow AppleSpell would
not be bad :)

While typing this, I notice that Mail.app only does on the fly checking at cursor position.

So that's a confirmation that even Mail.app developpers found the spellchecker to be slow.

That is what I thought.

Well, we can of course do better by caching the correctly spelled and the mispelled words within the spellchecker interface. This will requires some memory but this will improve the speed dramatically because of the reduced calls to the native Mac checker. A bit like what we do for gettext optimisation.

That may be a good idea indeed. I wonder how much memory this would cost.

JMarc

Reply via email to