Apache OpenOffice (AOO) Bugzilla – Issue 77592
Use of the Mac OS X spell checker
Last modified: 2007-10-09 06:16:44 UTC
keyword
Personally I prefer the current behaviour of the OpenOffice.org spell checker to the Mac OS X system wide spell checker. With the current implementation of the Mac OS X sell checker, if you correct one word through a right click, suddenly all the other red underlines in the text disappear.
This is new feature request. Any volunteers?
Using the Cocoa spell check functionality in a Carbon application is an example Apple has used for Cocoa-Carbon integration. See: http://developer.apple.com/documentation/Cocoa/Conceptual/CarbonCocoaDoc/Articles/CocoaInCarbon.html#//apple_ref/doc/uid/20002402-TP1 First step - make sure there is an acceptable way to use Cocoa in OOo macport.
I contacted one of the original implementers of spell check on OOO and he offered this advice: If you look at the lingucomponent module that includes with Hunspell, you can see how almost any spellchecker can be interfaced. Simply copy the module and use it as a model for interfacing to the MacOSX daemon. The interface is what you would expect. It can register itself (so that users can enable or disable that spellchecker), it gets called with a Unicode word and is asked to either spellcheck it or make a suggestion, etc. There really isn't much to the interface, all of the real work is done by the spellchecker itself.
.
CWS macosxspellchecker has been created with code to implement the spellchecker. I have tested en-US and fr, others are invited to test. Please note: If you do not do a full build you need to register the libspell680mxi.dylib with regcomp for the MacSpellChecker class to be recognized.
Michael, I have tested the fr version locally, and everything is ok. I have floowe your progress with the code, and that's fine too ( a review is needed, anyway). But as new feature, I fear they are "papers" to be created, with some ... administrative stuff. The only wish I have is use the Mac OS X Dictionnary. Last but not least: congratulations for your work :-) P.S. : I now see why I did not receive the notification for the cws: eric.bachard@free.fr is not the good email to be used. Can you please change for ericb@openoffice.org ? Thanks :-)
s/floowe/followed/ sorry
The cws has been updated, scp2 added, to deliver a separate dylib "libmacosxspell680mxi.dylib", implementing the Mac OS X SpellChecker functionality. I am sure there are many things yet to correct, but its basically working.
ericb->mikesic : can we consider the issue as fixed in macosxspellchecker cws ? ( urgent for integration )
added spec draft link
No problems reported from version August 29, 2007 until today - Sep 5, 2007
ericb->msicotte To avoid missing the deadline for Barcelone, I suggest you to set macosxspellchecker as Ready for QA. Jogi told me the specs are on the way.
I have added the reviewd specification to the CVS; I have added ericb as iTeam lead, mmp as UX man and TL as development member (review). Please feel free to add your comments. (Enable red lining, please that msicotte is able to accept or reject the changes!) msicotte, after we get the OK from the rest of the i-Team, you could add or reject the changes to the document under Edit / Changes / 'Accept or reject'
put the information on http://specs.openoffice.org/appwide/index.html
UX and string review done. Spec updated -> Please add a space to "SpellChecker".
Spec updated to match startup behavior. Attached - sorry but I don't yet know how to update it on the web site. A space added to make display name "Mac OS X Spell Checker".
Created attachment 48059 [details] Update to macosx_spellchecker spec - Sep 7, 2007
I found a test document (Samples_All_Languages.odt) on the OOo wiki with mis-spellings in many languages. I am attaching it here are an aid to testing.
Created attachment 48085 [details] Test document for spell checking
Created attachment 48180 [details] log of IRC discussion TL-ericb re spellchecker review
Created attachment 48182 [details] not authoritative list of spelling locales found on one Mac OS X system
please assign the issue to "jsi"
assigning to jsi
Created attachment 48222 [details] test case specification
seen in m229