Browse Prior Art Database

Method to Selectively Utilize Spelling and Grammar Correction Features Disclosure Number: IPCOM000035507D
Original Publication Date: 2005-Jan-21
Included in the Prior Art Database: 2005-Jan-21
Document File: 2 page(s) / 30K

Publishing Venue



Method to Selectively Utilize Spelling and Grammar Correction Features

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Method to Selectively Utilize Spelling and Grammar Correction Features

Currently when writing a technical document, an author will have several sections that are deeply technical and will be completely made up of text that will not pass the rules imposed by a grammar or spell check features supplied by the editor. This may be sections that show coding examples for a computer related document, examples of atomic interactions in a chemistry or biology technical document, etc. Aside from these technical sections, the rest of the document will contain typical structured paragraphs that will benefit from grammar and spell checking features. Currently, editors have do not have a way for the author to identify certain sections of the document that its spell and grammar checking tools should skip over or ignore. Therefore, the user is required to either select ignore on each word that the tools point out when performing a check of the document, or stop the tooling from running when they reach this section, move the cursor past the section, and restart the tool. Additionally, some editors try to make edit corrections for you on the fly, which becomes quite a nuisance when altering the deeply technical sections, but is desired when writing and editing the typically structured sections.

The core idea of this invention is for an editor to provide a feature that would allow a user to identify sections of the document that the grammar and spelling correction features should ignore. One way a user could identify these sections is by setting a starting point and ending point of the section within the text of the document. Another way the user could set this is by specifying that any section having certain font properties (such as type of Courier New and size of 10, color blue) should be passed over and ignored. This would be useful for these technical documents since oftentimes these deeply technical sections will use different fonts to visually differentiate them from the normal text.

For the purposes of illustration, I will use the example of writing a technical document which describes how to to address a specific programming issue. The deeply technical sections that contain words and syntax which a spelling and grammar corrections will therefore be sections of code. I will discuss a couple of ways which these sections could be identified to implement this art. However, there are a myriad of other possible implementations for this invention.

A user would begin writing their technical document as they normally do today. However, when they reach a section that they will need to write some code to give an example of what their text is describing, they might do one or the other (or a slightly different implementation option) of the following:

1. In the first example implement...