Add a spell checker to your Web page forms

Spelling Checker Engines

Home Site index Contact us Catalog Shopping Cart Products Support Search

You are here: Home > Add a spell checker to your applications > Web pages

Add a spell checker to your Web pages

Looking for a spellchecker that can spell-check text entered in HTML forms? You've come to the right place!

Wintertree Software has several products that can spellcheck text entered in web forms and HTML forms:

Use Wintertree Spelling Server to add server-side and client/server spellchecking under IIS (Windows NT, Win2000, XP). For more information, see Add a spell checker to your ASP/ASP.NET applications.

Use Sentry Spelling Checker Engine SDK for Java to add spell-checking capability to a Java applet (for client-side spell checking) or servlet. Sentry for Java comes with full source code for a sample Java applet and servlet. Click here to see a demo of the applet in action. For more information, see Adding a spell checker to a Java applet using Sentry Spelling Checker Engine Java SDK.

Use WSpell ActiveX Spell Checker to add spell-checking capability to Internet and Intranet Web pages viewed with Internet Explorer. For more information, see Using WSpell to check text in Web pages in Internet Explorer.

Use Wintertree Spell Check applet to add spell-checking capability to Internet and intranet Web pages with all browsers.

Which product is right for you?

Wintertree Spelling Server

Sentry for Java

WSpell

Wintertree Spell Check Applet

Client or Server?

Server. Includes a small applet that can optionally be used as a user interface on the client.

Applet: Runs entirely on the client

Servlet: Runs entirely on the server

Client

Client

Browsers and platforms

Works with all browsers. Requires NT-based server, IIS and ASP, Intel platform.

Applet: Compatible with most browsers.

Servlet: Compatible with all browsers. Server must support Java servlets.

IE (see Note 1)

Works with all browsers (browser upgrade may be required)

Programming required

Some VBScript programming is required. Includes example programs.

Java programming, plus general familiarity with applets and servlets, is required. Examples are included.

Some VBScript or JScript required. Examples are included.

Very small amount of JavaScript programming required. Examples are included.

Browser Security

Not applicable.

Applet: Works with signed and unsigned applets.

Servlet: Not applicable.

See Note 2.

Wintertree Spell Check Applet is unsigned. Digital signing not needed.

Site traffic

Usable in high-traffic sites with multiple simultaneous spelling-check requests

Servlet: Usable in high-traffic sites assuming server hardware has sufficient processing power

Not applicable.

Not applicable.

Client download requirements

Not applicable.

Applet JAR file is roughly 87K. American English dictionary is roughly 320K.

CAB file containing WSpell and American English dictionary is 240K.

Applet JAR file is roughly 87K. American English dictionary is roughly 320K.

Some of the issues you will need to consider in selecting a spelling checker for Web forms include:

Client or Server?

Spelling Checker running on the Client:

Processing is distributed among the client machines, so less load is placed on the server.

Browser security model makes client-based spell checking more complicated. Examples: Browsers prevent unsigned applets or controls from accessing files on the client machine, so dictionaries must either be loaded across the network or the spelling checker must be digitally signed.

Loading dictionaries across a slow network connection can take some time, leading to user frustration. Even the time required to download an applet or control can be significant.

Most browsers can run applets, but not all browsers on all platforms can run ActiveX (OCX) controls

Browser's Java library or JVM version may be incompatible with an applet

Spelling Checker running on the Server:

Spelling checker software and dictionaries exist in only one place, under one platform, so maintenance is less of a problem than in client-based solutions.

Works with all browsers, since Client/Server communication is generally though standard CGI protocol

Nothing needs to be downloaded to client, so there are no communication delays

Server must have sufficient resources (memory and processing power) to handle simultaneous spelling requests from multiple clients

Browsers and platforms

Some products will work only with certain browsers on specific client platforms, or with certain servers on specific server platforms.

Programming required

Some products require no programming beyond a little scripting, while others are software development kits intended to be integrated into applications by software developers.

Browser security

For security reasons, browsers limit the rights granted to applets and controls. Some of these limits can be lifted if the applet or control is digitally signed. Each browser type requires different kinds of digital signatures, and some browsers require users to grant specific privileges to signed applets/controls.

Site traffic

For server-based spelling solutions, the server must be able to keep up with the maximum number of simultaneous spelling requests received without incurring unacceptably long delays at the client.

Client download requirements

For client-based spelling solutions, all or part of the spell check software must be downloaded to the client. If the client uses a low-speed connection, the amount of information that must be transferred may result in delays.

Notes:

Note 1: ActiveX controls like WSpell work only with browsers running on 32-bit Windows systems. Internet Explorer can use ActiveX controls directly. Netscape can use ActiveX controls, but a plug-in is required in the client browser and the process involved with using an ActiveX control is complicated. WSpell has been tested with Internet Explorer, and comes with instructions for use with Internet Explorer. WSpell has not be tested with Netscape.

Note 2: If you intend to use WSpell in an Internet (as opposed to intranet) Web page, you may need to digitally sign a CAB file containing WSpell and its dictionaries. A CAB file signed by Wintertree Software, containing WSpell and the American English dictionary, is available. If you want to include different dictionaries, or want to sign the CAB file with your own signature, you must obtain a signature from a company like Verisign.

Home Site index Contact us Catalog Shopping Cart Products Support Search

	Wintertree Spelling Server	Sentry for Java	WSpell	Wintertree Spell Check Applet
Client or Server?	Server. Includes a small applet that can optionally be used as a user interface on the client.	Applet: Runs entirely on the client Servlet: Runs entirely on the server	Client	Client
Browsers and platforms	Works with all browsers. Requires NT-based server, IIS and ASP, Intel platform.	Applet: Compatible with most browsers. Servlet: Compatible with all browsers. Server must support Java servlets.	IE (see Note 1)	Works with all browsers (browser upgrade may be required)
Programming required	Some VBScript programming is required. Includes example programs.	Java programming, plus general familiarity with applets and servlets, is required. Examples are included.	Some VBScript or JScript required. Examples are included.	Very small amount of JavaScript programming required. Examples are included.
Browser Security	Not applicable.	Applet: Works with signed and unsigned applets. Servlet: Not applicable.	See Note 2.	Wintertree Spell Check Applet is unsigned. Digital signing not needed.
Site traffic	Usable in high-traffic sites with multiple simultaneous spelling-check requests	Servlet: Usable in high-traffic sites assuming server hardware has sufficient processing power	Not applicable.	Not applicable.
Client download requirements	Not applicable.	Applet JAR file is roughly 87K. American English dictionary is roughly 320K.	CAB file containing WSpell and American English dictionary is 240K.	Applet JAR file is roughly 87K. American English dictionary is roughly 320K.