NSSpellChecker (foundation) broken for custom NSSpellServer servers
NSSpellChecker (foundation) broken for custom NSSpellServer servers
- Subject: NSSpellChecker (foundation) broken for custom NSSpellServer servers
- From: Adam Strzelecki <email@hidden>
- Date: Wed, 6 Aug 2008 19:01:13 +0200
Hello,
I'm one of the supporters of custom NSSpellServer effort called
SpellCheck that does provide spell support for Eastern Europe
languages missing in Leopard built-in spell checker (We got Polish
interface but no Polish spell checker). SpellCheck uses Cocoa's
NSSpellServer interface, everything is working fine except there's
apparently a bug inside Foundation.framework regarding calls to proper
Spell Servers (via Mach ports).
It seems Foundation is often stubbornly calling wrong spell server.
AppleSpell.service NSSpellServer is registered with
registerLanguage:byVendor: for "en", "fr" .. etc. languages and
"Apple" vendor.
CheckSpell.service NSSpellServer is registered for exclusively other
languages as "pl", "cs", "lt", "lv", "sk" ... with "Apple" vendor
(also I checked changing to "Check" vendor, same problem).
So it often happens that Foundation calls CheckSpell.service for "en"
and vice-versa AppleSpell.service for "pl"! This happens by instance
in Mail.app, when I first use English spell checking via
AppleSpell.service, and switch to Polish (pl) via CheckSpell.service
for my next mail, Foundation (NSSpellChecker) is getting crazy, and
asking AppleSpell for "pl", which results in totally wrong (empty)
response. In order to get proper "pl" via CheckSpell.service I need to
restart Mail.app, but then when I want to switch to English, ..... yes
again I need to restart.
This thing is really bothering me much in OSX, I was writing to
Apple's feedback regarding OSX and Mail.app about this issue once
there was just 10.5.0 release, since then nothing has changed, this
bug is still there unfixed.
Maybe someone from Apple OSX devs is reading this list, and could take
a peek into this problem?
I'm aware there's a bug tracker for paid & registered Apple
developers, where I could report those problems, but since I'm not one
of them I have no access there.
Thanks,
--
Adam Strzelecki | nanoant.com
P.S. Also very very annoying thing about Cocoa is that changing spell
language with ⇧⌘; does not revalidate all words in NSTextView, but
only current word under the cursor, so either I need to scroll trough
whole document to have the text revalidated with new language or I
need to press Next many many times in Spelling & Grammar window. I
believe it would make life easier for double- or tripe- language
writers under OSX so whole document gets automatically revalidated
once I switch the language._______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden