With all due respect to the work you have done, I believe spell checking is the domain of the client.
On Safari (MacOS X) at least, client-side interactive spell checking works great with MediaWiki. Does it not in other browers/OSs?
:::: Faith in the Universe is ultimately faith in one's self. :::: Jan Steinman http://www.Bytesmiths.com/Item/770301
On 7/19/05, Jan Steinman Jan@bytesmiths.com wrote:
With all due respect to the work you have done, I believe spell checking is the domain of the client.
On Safari (MacOS X) at least, client-side interactive spell checking works great with MediaWiki. Does it not in other browers/OSs?
SpellBound 0.7.3 Spellchecker for Firefox and the Mozilla Suite
http://spellbound.sourceforge.net/
Steven Hilton wrote:
On 7/19/05, Jan Steinman Jan@bytesmiths.com wrote:
With all due respect to the work you have done, I believe spell checking is the domain of the client.
On Safari (MacOS X) at least, client-side interactive spell checking works great with MediaWiki. Does it not in other browers/OSs?
SpellBound 0.7.3 Spellchecker for Firefox and the Mozilla Suite
There's also ieSpell v2.1.1 for Explorer (http://www.iespell.com/).
The problem, of course, is that exceedingly few Wiki users -- or, at least, users of my Wiki -- are going to be apt to have either product (despite the fact that I list them on my help page). I presume that server-side spell checking does not preclude one from using a client-side spell-checker, so I'm really at a loss as to why -- aside from the seemingly inevitable naysaying so common to this list -- a server-side spell checker is such a bad idea. But then I'm sure someone will be along shortly to explain why it is bad for the internet, violates the Wiki concept, or creates mopery and dopery on the spaceways.
Myria
"Myria" myria@wolfandturtle.net wrote in message news:000001c58d30$301cd630$6500a8c0@Lappy...
.... I presume that server-side spell checking does not preclude one from using a client-side spell-checker, so I'm really at a loss as to why -- aside from the seemingly inevitable naysaying so common to this list -- a server-side spell checker is such a bad idea. But then I'm sure someone will be along shortly to explain why it is bad for the internet, violates the Wiki concept, or creates mopery and dopery on the spaceways.
The main objection on :en: would be the inevitable arguments as to whether to use US or UK English.
It **might** be possible to arrange for an option wherein a particular spelling dictionary could be selected for a given article, but the scope for spelling-reversion-wars would be immense.
OTOH for those wikis which use a single well-defined mode of spelling, this might well be very helpful for non-native contributors.
Assuming they pick the correct option obviously: we are awl familiarity with thee pecuniary problematic of spell-cheque systemic :-)
Has anyone taken a shot at writing an extension to use Google's Spell Check API? If not I might take a show at it. Be interested to here Brions thoughts on this.
Simple example on how to do SOAP calls to the Google API's: http://www.phpbuilder.com/columns/adam_gundry20050316.php3
-ben
On 7/20/05, Myria myria@wolfandturtle.net wrote:
Steven Hilton wrote:
On 7/19/05, Jan Steinman Jan@bytesmiths.com wrote:
With all due respect to the work you have done, I believe spell checking is the domain of the client.
On Safari (MacOS X) at least, client-side interactive spell checking works great with MediaWiki. Does it not in other browers/OSs?
SpellBound 0.7.3 Spellchecker for Firefox and the Mozilla Suite
There's also ieSpell v2.1.1 for Explorer (http://www.iespell.com/).
The problem, of course, is that exceedingly few Wiki users -- or, at least, users of my Wiki -- are going to be apt to have either product (despite the fact that I list them on my help page). I presume that server-side spell checking does not preclude one from using a client-side spell-checker, so I'm really at a loss as to why -- aside from the seemingly inevitable naysaying so common to this list -- a server-side spell checker is such a bad idea. But then I'm sure someone will be along shortly to explain why it is bad for the internet, violates the Wiki concept, or creates mopery and dopery on the spaceways.
Myria
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Jan Steinman wrote:
With all due respect to the work you have done, I believe spell checking is the domain of the client.
On Safari (MacOS X) at least, client-side interactive spell checking works great with MediaWiki. Does it not in other browers/OSs?
Spell-checking in Safari is lovely, and I too am surprised this isn't fully standard on many other popular browsers yet. However there are some problems:
* The client's checker will only come with a certain number of spelling dictionaries by default; some languages will not be present.
* It may be fairly annoying to switch the language selection on the client, and it may not automatically follow with the declared content language of the site.
* Of course lots of people don't have the capability in their browsers to begin with.
So, it could be worthwhile even though a proper, complete implementation in the client is preferable.
-- brion vibber (brion @ pobox.com)
mediawiki-l@lists.wikimedia.org