Abstract:
A technique for providing simplified and more flexible text recovery in an electronically stored text. The text storage device is of the hand-held type and may accommodate the text of the entire bible, for example. The user may access the stored text in a read or search mode. The device is programmed to perform certain functions automatically, such as: selecting search or read mode; accommodating different syntax formulations; providing a fixed screen map of respective different portions of the text; and visually indicating specific words of a search to which a search will be limited. Expanded flexibility is also programmed into the device which includes: optionally expanding searches to cover both different forms of the same words and unrelated words having the same meaning; providing assistance to the user upon request which takes into account the current operational phase; and providing the capability of tagging a preselected location in the text for simplified access during reacquisition.

Description:
This is a continuation of application Ser. No. 08/036,622, filed Mar. 24, 1993, now abandoned, which was a divisional of application Ser. No. 07/529,867, filed May 29, 1990, now abandoned. 
    
    
     CROSS REFERENCE TO RELATED APPLICATION 
     Reference is made to the application entitled &#34;Electronic Text&#34; by the same inventor filed simultaneously herewith. The contents of that application are incorporated herein by reference. 
     MICROFICHE APPENDIX 
     A microfiche appendix is attached having 6 microfiche and 311 pages. 
     BACKGROUND OF THE INVENTION 
     The present invention relates to techniques for accessing textual information stored in an electronic memory and for providing simplified and more flexible text accessing techniques to the user. 
     More particularly, the present invention relates to an electronically stored text in a hand-held device having a keyboard and screen wherein various keys in distinct sequences may be actuated to interactively provide different modes for analyzing the text. The device is programmed to minimize user interaction in a number of such modes. 
     Electronic devices for providing word-related operation and manipulation are known. Such devices, such as the Electronic Spelling Machine disclosed in U.S. Pat. No. 4,830,618, include a keyboard, screen and permanent electronic storage, i.e., a read-only memory. Techniques for the retrieval of individual words, however, are not necessarily appropriate when dealing with electronic storage of a complete comprehensive text. 
     When considering the presentation of a full text, such as the Bible, in a hand-held machine intended for personal and repeated use, it is important to provide techniques which avoid excessive keyboard manipulation and at the same time provide a variety of approaches for accessing, using and reusing the stored text. 
     It is an object of the present invention to provide a simplified but varied and effective technique for accessing electronically stored textual information. 
     It is a further object of the present invention to provide such a technique in a hand-held text storage machine. 
     In accordance with the invention, in a method for providing user access to stored textual information in an electronic book, the method having search and read modes of access, the improvement comprises providing simplified and more flexible user operation steps. These steps include selecting search or read mode automatically, accommodating different syntax formulations of an entry word or phrase in the read mode, optionally expanding searches to cover different forms of the same word and unrelated words having the same meaning, providing the capability of tagging a preselected location in the text for simplified access during reacquisition of textual information, providing a map of different fixed locations on the screen corresponding to respective different portions of the text, providing assistance to the user upon request which takes into account the current operational phase and visually indicating specific words of a search request to which a search will be limited. 
     For a better understanding of the present invention, reference is made to the following description and accompanying drawings while the scope of the invention will be pointed out in the appended claims. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     Referring to the drawings, 
     FIG. 1 is a perspective view of an embodiment of the present invention; 
     FIGS. 2a-2g are flow charts indicating the significant logical steps in effecting the various features of the present invention; and 
     FIG. 3 is a schematic representation showing the multi-level search aspect of the present invention. 
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     An embodiment of the present invention shown in FIG. 1, incorporates, as stored text, the King James version of the Holy Bible. 
     The device 10 includes a keyboard 11 and screen 12. The keyboard 11 presents the standard keys of an ordinary typewriter and other more or less standard operating keys of a word processor. The latter include the CLEAR, MENU, HELP, ENTER, EXIT and CURSOR CONTROL KEYS. An ON/OFF control is also included. 
     The user of any stored textual material may desire to read designated sections, e.g., chapter and verse of the Bible, or may desire to find a specific section by entering a key word or words (by searching). 
     Automatic Mode Selection 
     In the device of the present invention, these two basic functions, &#34;read&#34; and &#34;search&#34;, are determined automatically without requiring user mode selection. This is done by the device 10, by parsing the input string (the word or words entered on the screen) and switching into the appropriate mode. 
     Specifically, the user need only press the ON/OFF switch, type in the inquiry, press ENTER and get a result. The results will require further steps such as selection within the result (discussed below) or advancing the text in order to read the text presented. The important thing is that the user obtains the result after entering the inquiry without having to select a mode. 
     The parsing operation is defined as follows. 
     The user&#39;s query is submitted to the parser, which tries to parse it as a read-mode request. Read-mode requests consist of a &#34;book&#34; (with optional &#34;volume&#34; specifier attached), an optional &#34;chapter&#34;, and (if a chapter has been specified) a &#34;verse&#34;. If a query fails to parse as a read-mode request, the parser BAILS OUT and treats it as a search request. 
     The parser starts at the beginning of the query. If it manages to isolate a book/volume name, it moves past this and then, from its new position in the query, attempts to isolate a chapter specification, etc. 
     A flow chart of the automatic mode selection step is presented in FIG. 2a. 
     In FIG. 2a, all of the paths are directed to whether the query or request is a read-mode request. Starting with the user&#39;s query, the first step is to determine whether a book or volume name can be isolated. If so, the next step is to determine whether a chapter specification can be isolated. If so, the next step is to determine whether a verse specification can be isolated. If so, and if the query is exhausted, it is determined that this is a read-mode request. 
     Other flow chart paths indicated which result in a read-mode request assume verse 1 or assume chapter 1, verse 1. One flow chart path questions whether the book name is also a word that occurs in the lexicon which, if yes, triggers a request to the user as to whether to read the book or search the word. This results in either a read-mode request or search mode request depending on the response. 
     In various steps of the chart, failure leads to a &#34;bail out&#34; condition, this is a last ditch attempt to interpret the query as a read-mode. What is done is to determine whether the query contains any numerals 0-9. If not, then it is determined that it is a search mode. If so, it is decided that it is a read mode request and the user is told that the book mode cannot be recognized and the user must edit and re-try the query. 
     There are certain situations in which the input is inherently ambiguous as to whether the &#34;search&#34; mode or &#34;read&#34; mode is required. Thus, for example, if an individual enters LUKE, it is not clear as to whether the individual wishes to read the books of LUKE or wishes to locate all of those positions in the Bible where the name &#34;Luke&#34; appears. In such situation, the machine will ask the user to select whether to &#34;read&#34; or &#34;search&#34; by selecting one of two keys (e.g. 1 for read or 2 for search) 
     Bookmark Function 
     The device provides the user with the ability to electronically &#34;tag&#34; a certain number of text locations much like a bookmark for quickly and automatically returning to those locations. 
     The preferred embodiment provides four such bookmark locations. To set a bookmark at a particular location, the &#34;MENU&#34; key is pressed followed by the &#34;B&#34; key. After setting of the bookmark, when the MENU key is pressed, the various set bookmarks appear on the screen. Any one may be selected by pressing the &#34;B&#34; key followed by the numerical key (1 or 2 or 3 or 4) for the desired bookmark. 
     A flow chart is presented in FIG. 2b illustrating the logical steps for setting a bookmark and for going to a marked location. 
     In determining and using a bookmark, it is understood that there are a given number of &#34;bookmarks&#34; supplied that are each either empty or assigned to a location in the electronic book. Bookmarks are set by first, reading the biblical text; second, pressing menu -B to select the bookmark function; third, pressing a number corresponding to an &#34;empty&#34; bookmark; then the program automatically assigns assigns the empty bookmark to the current location and the reader is returned to the text. 
     The system permits going to a pre-marked location by first, pressing menu -B to select the bookmark function; second, pressing the number corresponding to an assigned bookmark; third, automatically taking the reader to the location assigned to the bookmark. 
     Syntax Accommodations 
     A significant simplification provided by device 10 is the internally programmed provision to accommodate a wide variety of formulations in the &#34;read&#34; mode. For example, I KINGS or KINGS I will get the reader to the same place in the text. The device has a grammar of syntaxes such that all of the following will result in the same read position being brought up on the screen: 
     IKG 
     KING I 
     KG1 
     FIRST KINGS 
     I KINGS 
     The following table illustrates the scope of these syntactical accommodations (=space character(s)): 
     
                       TABLE I______________________________________I.   Booknames:1.     Books without May be specified by the  &#34;volume number&#34;                full name or any two-or-more                character abbreviation that                begins with the first character                of the name, and omits letters                at the user&#39;s discretion.                The abbreviation will work,                provided it is unique to one                book.                e.g. for the book &#34;MATTHEW&#34;,                the following are adequate:                MT, MAT, MATT, MW, MTW,                etc. but not MH, since this                could also stand for                &#34;MICAH&#34;.2.     Books with    The book name exclusive of  a &#34;volume number&#34;                the volume number may be                abbreviated as described above.                The understood formats for                volume number are illustrated                below for the book &#34;2                CORINTHIANS&#34;ROMAN NUMERALS:          II COR       COR II          IICOR        (CORII not                       recognized)SPELLED OUT    SECOND COR   COR SECONDVOLUME #:      SECONDCOR    CORSECONDCARDINAL NUMBERS:          2 COR        COR 2          2COR         COR2ORDINAL NUMBERS:          2ND COR      COR 2ND          2NDCOR       COR2ND (Note we have used the &#34;COR&#34; abbreviation for &#34;CORINTHIANS&#34;. Any legal abbreviation according to section 1 will work). 
    
     
         II.  Chapter Specification:Recognized Formats:               1.    &#34;1&#34; &#34;5&#34; &#34;26&#34;, etc. (simple                     cardinal numbers)               2.    &#34;CHAPTER 5&#34;               3.    &#34;CHAP 5&#34;, &#34;CHAP5&#34;III. Verse Specification:Recognized Formats:               1.    &#34;1&#34;, &#34;5&#34;, etc.               2.    &#34;VERSE 5&#34;, &#34;VERSE5&#34;______________________________________ Final note: The book/volume name, chapter specification, and verse specification may but need not be separated from each other by space characters in the user&#39;s query. Exception: Cardinal numerals (0-9) may not be adjacent if they do not belong to the same number; i.e. the chapter number and verse number must be separated b at least one space if there is no &#34;VERSE&#34; string in between. 
    
     Triple Level of Linguistic Range (Search Expansion) 
     The device will, in the first instance, search a designated word, and its possessive, and its capitalized forms (level 1). An example of a level 1 search is that a search for the word KING will cause a search for the following: king, king&#39;s, King, King&#39;s, KING. A total of 5 forms are searched simultaneously. It should be noted that level 1 obviates the need for having apostrophe and &#34;shift&#34; keys on the keyboard. 
     This search may be expanded in two additional ways. A second expanded level (level 2) of a search is provided by pressing the single &#34;?&#34; key, which choice is listed on the MENU (following the pressing of the MENU key). The device expands the search by using all forms (inflections as well as other syntactically related words) of the entered words. For example, the entry of the words MOVE WATER will initially find no correspondence in the search of the bible text. By expansion to include &#34;moved&#34; and &#34;waters&#34;, a number of locations in the text corresponding to variations of these words will be found. The search could be started by first entering &#34;MOVE? WATER?&#34; to indicate that all forms of the words are to be searched in level 2. If &#34;move water&#34; were entered initially with no &#34;?&#34;s a rapid way of adding the &#34;?&#34;s to each word without retyping is to press the MENU key and then the &#34;?&#34; key. 
     A further level of search expansion (level 3) will expand the search by utilizing words which are different but similar in meaning such as provided in a Thesaurus. For example, &#34;water&#34; and &#34;sea&#34; would be equivalent words from this point of view. This is particularly helpful in searching for passages on a given theme in an electronic text or for words recalled from a different translation of the text source. In order to do this, the user is required to insert a double question mark following each word of the search phrase. For example, a phrase which may be entered is &#34;VOICE ?? CALL ?? DESERT ??&#34;. This would eventually develop among the various places to be read the following at Isaiah 40:3: 
     &#34;The voice of him that crieth in the wilderness, Prepare ye the way of the LORD, make straight in the desert a highway for our God.&#34; 
     A more experienced user may wish to mix different search levels in his or her search request. This may be done freely on different words of the query, for example: &#34;VOICE CRY? DESERT??&#34; will also find Isaiah 40.3 (cf., with p. 9, lines 23ff). All three search levels are expressed in this request. 
     FIG. 2c is a flow chart illustrating the three levels of linguistic range possible with the device. 
     For each word in a search-mode query, the device will perform the following processing. First, a word is provided by the user as a query. From this, a search &#34;list&#34; is begun to be built with this word. The first level of search list is formed by automatically adding certain forms to the search list if they occur in the lexicon. These include possessive forms, a capitalized form, a capitalized possessive form and an all uppercase form. The word in the query is then followed by a &#34;?&#34; to do a first level search; a &#34;NO&#34; response will take the search list related to this word, which acts as a single token in the search query (any match to a word on the list is treated as a match to the user&#39;s word). 
     If the user responds &#34;YES&#34;, then a second level search list is formed which adds to the search list all inflected forms of the word, and compound words derived from it. The word query is then followed by &#34;??&#34; to do a second level search. Once again, a &#34;NO&#34; response will take the search list related to this word to find any match to a word on the list which is treated as a match to the user&#39;s word. 
     If the user responds &#34;YES&#34;, added to the search list are words related in meaning plus their inflected forms to generate the third level of search. This level is used to find any match to a word on the list which is treated as a match to the user&#39;s word. 
     In FIG. 3, the system RAM and ROM controls the application of the stored program for the three search levels which are all handled in the microprocessor. 
     In a further variation of search expansion, the expansion terms may be added or rejected one by one in a non-automatic manual mode. This is known as the &#34;Approvals&#34; mode obtained by first pressing the MENU key followed by the designated key for approvals (&#34;A&#34;). 
     Display Map 
     In the Biblical embodiment for the electronically stored text, each book that may have text relevant to the entry word or phrase is displayed at a fixed location on the screen. Thus all of the books of the Bible have their own separate positional display location on the screen. The screen location of each book is always fixed. Only those books which are relevant are displayed at any time after a query is submitted by the user. This includes displaying which books contain matches to the user&#39;s query. A &#34;flashing&#34; icon representing a particular book selection serves as a cursor to assist the reader to indicate which book the user is in while reading the text. The display map in essence is an animated map of the stored text and provides a continuous &#34;image&#34; of the operational state of the device. The fixed display location for each book and the &#34;flashing&#34; icon representing a book while its text is being read greatly facilitate utilization of the device by the user. 
     FIG. 2d is a flow chart illustrating the use of the display map in both &#34;read&#34; and &#34;search&#34; modes. 
     The display map is obtained in read mode in response to a read request. This causes the book icon to light up; the user enters the book and begins to read. In response to a search request, all books which contain a match to the query light up. The user then selects one of the lit book icons. The system enters this book at the location of the first match; only this book icon is then lit up and the user can read. The user can either press &#34;exit&#34; to select a different book or, using &#34;N&#34; and &#34;P&#34; keys (and &#34;S&#34;), the user jumps from match to match, sometimes going from one book to another. The appropriate icon is always the only one lit up. Once again, the user may press &#34;exit&#34; to select a different book. 
     Search Denotation 
     A further programmed simplification is that the device will designate, by underlining, which words of a phrase will be searched in the &#34;search&#34; mode. For example, when the phrase &#34;the meek shall inherit the earth&#34; is entered, only the significant terms &#34;meek&#34;, &#34;inherit&#34; and &#34;earth&#34; are actually searched. These words are underlined so that the user knows that the search is limited to those three significant words. The device then performs a search limited to only these words of the phrase. 
     FIG. 2e is a simplified flow chart illustrating how the device will limit a search request. 
     As indicated in the flow chart, the user enters a multi-word query; the user then starts the search; the system then looks up each word in the query. If a word is in the &#34;concordance vocabulary&#34; it is underlined. Otherwise, it is ignored for the purpose of the search. The search is then carried out, ignoring all non-underlined words in the query. 
     Context-Sensitive &#34;Help&#34; System 
     In prior techniques involving reading or searching electronically stored material, the pressing of a &#34;HELP&#34; key would provide descriptive assistance to the user on the screen. Such assistance, however, was of a predetermined, fixed form and was not related to the then current operating situation. 
     In the present device, by distinctly defining the internal operational phases, user assistance is provided which is directly related to the current operational point reached by the user. The user is provided with appropriate options related to the operational point reached. 
     FIG. 2f provides a flow chart for illustrating this context-sensitive &#34;Help&#34; system. 
     Assuming a question on the part of the user, he or she presses a &#34;HELP&#34; key at any point in the operation. The system then determines where the user was (thus essentially divides the operation into well-defined phases). Appropriate HELP screens are then displayed providing various immediate options to the user. The user then reads the HELP information. The user, following use of the HELP information then may press the EXIT key. It is also possible to press HELP while searching HELP information and receive information about the HELP system. 
     &#34;Pruning&#34; of Linguistic Range Expansion 
     The flow charts (2c, 2g) make reference to &#34;the lexicon&#34;, (well defined in the simultaneously filed application incorporated by reference herein), i.e., the product&#39;s internal lexicon of words making up the text. Linguistic range expansion is always, at each step, &#34;pruned&#34; by the lexicon, as further illustrated in flow chart 2g. This pruning happens quasi-automatically as programmed into the device. 
     In the flow chart, the input is that the word in the user&#39;s query is not in the text lexicon. It is then determined if it is a missing root. If so, a &#34;?&#34; is added automatically which generates a level 2 search. 
     If not, it is then checked to see if it is in the thesaurus. If so, a &#34;??&#34; is added automatically generating a level 3 search. If not, the spelling correction is run for this word. 
     If any word in the user&#39;s query is not found in the lexicon of the text, a series of steps is performed as follows: 
     1. The device has a list of &#34;missing root words&#34;. These are words which have inflected forms that occur in the text, but the simplest form does not; e.g. the word &#34;babble&#34; is not in the Bible, but &#34;babbler&#34; is. If the user&#39;s word is one of the &#34;missing roots&#34; (like babble), a single ? is added absolutely automatically by the device, which generates a level 2 search with no keystrokes pressed. 
     2. If the word does not match the missing root list, then it is checked to see if it occurs in the thesaurus. If it occurs, a double ? is added, generating an automatic level 3 search. 
     3. If both steps 1 and 2 fail, then the device assumes a misspelling, and the spelling corrector is run. 
     The Annexed Listings (Appendix A) 
     Appendix A is a microfiche version of all of the listings required for programming a complete electronic book (Bible) including the inventive features described above the listings are in two parts: a Program Listing (approximately 200 pages) of the internal operations of the device and a Primary Compression Method Listing (approximately 92 pages) for compression of the Biblical text. The inventive features of the present application are included in the first listing together with other functions (e.g. display, enter etc.) not forming part of this invention. The Appendix A listing is primarily in C code with a small amount of assembly code. 
     The above embodiment of an electronic text, the Bible, is only one example of the general case of electronic stored text information. The &#34;book, chapter and verse&#34; reflects, in terms of the Biblical embodiment, the fact that in a text, locations are often specified with multiple components (some of them omittable). 
     While the foregoing description and drawings represent the preferred embodiments of the present invention, it will be obvious to those skilled in the art that various changes and modifications may be made therein without departing from the true spirit and scope of the present invention.