[ 0025 ] fig1 illustrates a web page screen display 100 showing the use of hyperlinks in an exemplary embodiment of the present invention . a hyperlink is an active area (‘ hot area ’) in a displayed document that when ‘ clicked ’ on ( e . g ., by a mouse ), causes the user &# 39 ; s browser to load an entity referenced by a url ( universal resource locator , which specifies the internet address of the referenced item ). an anchor is an area within the content of a hypertext node ( e . g . a web page ) which is the source or destination of a hyperlink . a source anchor may be a word , phrase , image , or possibly the whole node . a destination anchor may be a whole node or some position within the node . typically , clicking with a mouse on a source anchor causes the link to be followed ( by the user &# 39 ; s web browser ) and the anchor at the destination end of the link to be displayed . a destination anchor is simply an anchor placed in a file at a hyperlink destination . anchors are typically highlighted in some way ( either always , or when the mouse is over them ), or they may be marked by a special symbol . in html ( hypertext markup language ), anchors are created with the & lt ; a ..& gt ;..& lt ;/ a & gt ; construct . the opening a tag of a source anchor has an href ( hypertext reference ) attribute giving the destination in the form of a url — usually a whole node or ‘ page ’. consider the following hyperlink definition : when a user clicks on the ‘ hot area ’ ( source anchor ) represented by “ click here ”, the document “ next . html ” will be loaded into the window or frame named “ window .” the anchor (& lt ; a & gt ;) tag is the html feature for defining both the source and the destination of the hyperlink . as shown in fig1 a hyperlink is conceptually represented by arrow 103 between a hyperlink source 101 ( 2 ), which is located in a first data file , and a hyperlink destination 104 ( 1 ), which can be located in the same or in a second data file . as shown in fig1 text window 108 includes a plurality of ( i . e ., n ) textual or graphical hyperlink source entities 101 (*) [ where the ‘*’ symbol indicates a wildcard representing any member of the class of items having the same basic reference number ], indicated as index ( 1 )— index ( n ). each text entity ( hereinafter referred to as an index ) 101 (*) has an associated html source anchor . for example , index ( 2 ) [ reference number 101 ( 2 )] has the associated anchor 102 , which has subindex ( 1 ) 104 ( 1 ) as its destination in target window 109 . the hyperlinked association between index ( 2 ) and subindex ( 1 ) is indicated by arrow 103 . alternatively , a source anchor in window 108 , such as index ( 2 ) may have a destination anchor in a different window , as indicated by arrow 107 to destination (‘ target ’) text 111 in window 110 . the present example is set in the context of a web page 100 that is used for displaying ‘ help ’ information about a system . for example , the items depicted by indices index ( 1 )— index ( n ) [ reference numbers 101 ( 10 - 101 ( n )] may be categories of system commands , such as “ script ” commands or “ run ” commands , for which a user desires information . one of the text entities , e . g ., index ( 1 ), may be a category that includes all of the commands ( or other entities ) for which a target text entity 111 may be displayed . when a user of the present system selects a particular command category , by clicking a mouse on the category name , a list of all of the commands in the category are displayed in a separate window . for example , if index ( 2 ) in window 108 indicates “ run commands ”, when the user selects ( clicks on ) the corresponding hot area 101 ( 2 ) associated with index ( 2 ), the text entities ( sub - indices ) subindex ( 1 ), subindex ( 2 ), and subindex ( 3 ) in window 109 [ shown by reference numbers 104 ( 1 )- 104 ( 3 )] will then be displayed as a list of members of the selected category of commands such as “ continue ”, and “ continue_one ”, and “ step ”, respectively . if the user then desires to see the specific help information , e . g ., for the “ step ” command , the hot area [ subindex 104 ( 3 )] for this command is selected ( clicked on ) in window 109 , and the associated (‘ target ’) text 111 is displayed in main window 110 on the web page screen display 100 . the mechanism by which these operations are performed is explained below in detail with reference to fig2 , 4 a and 4 b . alternatively , the items depicted by text entities index ( 1 )- index ( n ) may be topics in a document ( instead of system commands ), in which case the text entities subindex ( 1 )- subindex ( m ) are related subtopics or subjects , i . e ., names of members of the class denoted by the selected index 101 (*). in this case , the target text 111 displayed in target window 110 describes the selected subtopic or subject , rather than a system command . the html frame for the screen display 100 is generated by copying common files , for example , a gif file for the basic web page frame graphics , a . css file that describes the frame , and the index . html frame ( the display screen html frame that points to the text for windows 108 / 109 . these common files are stored in a known location , such as in the command name directory 212 , described below with respect to step 435 . [ 0036 ] fig2 is a block diagram illustrating basic data components in an exemplary embodiment of the present system . as shown in fig2 help text file 210 contains all of the help documentation , in plain text or ascii format , for the system of interest . operation of the present system is best understood by reference to fig2 in conjunction with the flowcharts of fig3 a , and 4 b , as described below . fig3 a , and 4 b are flowcharts illustrating an exemplary sequence of steps performed in carrying out one embodiment of the present system . as shown in fig2 and 3 , at step 305 , all of the help text documentation ( or other documentation of interest ) in a software program or other file ( the ‘ initial documentation ’) 205 is loaded into help text file 210 . at step 310 , help text file 210 is then processed by a hyperlink processor program , the details of which are explained below with respect to fig4 a and 4b . table 1 , below , shows an exemplary format for three of the entries in the help text file 210 , which contains a number of entries equal to the number of commands or subjects which may be separately referenced ( e . g ., the number of text entities 111 which can be separately displayed in target window 110 ). each entry in the file is separated by the delimiters “ command :” and “ end :”, and the delimiter “ help :” is employed to indicate the beginning of the help text for each command entry . these delimiters are generated and inserted when the help text file 210 is generated . as shown in fig4 a , at step 410 , global index file 214 , containing a list of all of the commands ( or other index words ), is created by reading help text file 210 and inserting , in order , each of the command names found in file 210 into the global index file 214 . the html code for the hyperlinks used in the present system is generated at this step . the help text file 210 and the global index file 214 are generated using two input files , the text documentation files in the initial document 205 , and a manually generated main category file 215 . from these two files , global index file 214 , an index category file 230 (*) for each category in the main category file 215 , and a command name file 220 (*) for each command in the help text file 210 , are generated . these files are described in detail below . exemplary contents of global index file 214 are shown below in table 2 . at step 412 , a set of command ( or subject ) categories is determined , using arbitrary category names as desired . step 412 may be performed at any time prior to creating the main category file in step 415 , below . at step 415 , a main ( command ) category file 215 is manually created . each of the commands ( or alternatively , subjects ), for which help text is generated , is manually assigned to one or more named categories , and placed in the main category file accordingly . each category is delimited by a percent sign in the first column of the line . the name of the category follows and has no restrictions . each command that belongs in a particular category is listed on a separate line . every command from the start of a particular category to the start of the next category is considered to be a command belonging to that particular category . commands may belong to any number of categories , as shown in table 3 below , wherein the “ source ” command is included in the “ script commands ” category , as well as in the category named “ test category ”. an exemplary segment of main category file 215 is shown in table 3 , below . at step 420 , main category file 215 is read to determine the indices in which each command should be placed . at step 425 , each command ( or subject ) in main category file 215 is associated with one or more indices , using the correspondence set forth in the file 215 . at step 430 , each command ( or subject ) is inserted into data structure 216 , wherein each command is associated with the appropriate indices as indicated by the command - to - category association of step 425 . the data structure shown below in table 4 is a perl language hash table , wherein each hash has multiple values per key , and each key is an array . it should be noted , however , that any type of array mechanism could be employed to provide the desired association between each command and one or more relevant categories . at step 433 , text in help text file 210 is copied to an intermediate working directory , referred to as command name directory 212 . global index file 214 , command name files 220 (*) and index category files 230 (*) ( described below ) are also copied to this directory . a segment of a subdirectory named “ help ”, containing html files for the individual command categories , as well as the command names , located in command name directory 212 , is shown below . the run_commands . nav . html file , for example , contains the following list of commands : all of the files generated by the present system are located in the command ( subject ) name directory 212 . at step 433 , index category files 230 (*) are present , but do not yet include any hyperlinks . hyperlinks are added at step 470 , described below . [ 0049 ] fig4 b illustrates an exemplary instruction loop for parsing the help text file 210 to create command ( subject ) name files 220 ( 1 )- 220 ( n ) and index files 230 ( 1 )- 230 ( m ). as shown in fig4 b , at step 440 , one or more lines of data is read from help text file 210 . at step 445 , if a beginning ( command name ) delimiter ( e . g ., “ command ”) is encountered in the data read from the help text file 210 , then an command name file 220 (*) is created for the term appearing in the line in the file 210 following the delimiter . each command name file 220 (*) contains html - encoded text for the associated command ( or subject ). to help illustrate the steps shown in fig4 b , the “ step ” command shown in table 1 is used as an example : command : step step [& lt ; count & gt ;] help : single step the current cpu for & lt ; count & gt ; instructions ... end : in the above example , it can be seen that the line following the beginning delimiter “ command ” contains the text “ step ”. in accordance with the present system , a command name file 220 (*) containing the html code for the present command is generated at step 460 . in the present example , a command name file 220 (*) named “ step . html ” containing the html code for the “ step ” command is generated . the html for step . html is shown below in table 5 . at step 465 , a hyperlink is created from global index file 214 to the appropriate command name hitml file 220 (*). for example , the hyperlink for the “ step ” command might appear as : the above hyperlink links index ( n ) [ reference no . 101 ( n )] in window 108 with the corresponding subindex ( m ) [ reference no . 104 ( m )] in window 109 . at step 470 , hyperlinks are then created from the indices ( categories ) in data structure 216 to the associated command name files 220 (*). as an example , the index ( category ) file containing hyperlinks from the run commands category to the associated commands in that category is shown below in table 6 . a branch back to step 435 is then taken , where a check is made to determine whether there is any remaining unread data in help text file 210 . if all of the data in the file 210 has been read , then the parsing of help text file 210 is completed , and processing resumes as shown in fig3 beginning at step 315 ( described below ). if more data remains in the help text file 210 , then steps 440 through 445 are repeated , as described above . at step 445 , if a beginning delimiter is not encountered , then a check is made for a “ help ” delimiter , identifying the beginning of the help text , at step 450 . if a help delimiter is found , then , at step 455 , the help text is copied from help text file 210 to the appropriate command name html file 220 (*). processing of help text file 210 then continues , at step 435 , until the end of the file is encountered . if a help delimiter is not found , then , by default , the remaining data ( line ) in the file must be an “ end ” delimiter , and the command name html file 220 (*) that was just generated is closed , at step 451 . at step 315 , the hyperlinked output generated in the above steps ( shown in fig4 a and 4b ) is copied to the appropriate web server ( not shown ). finally , at step 320 , links on web page 100 are updated by the present system to point to the new ( or modified ) version of the help documentation created in accordance with the process described above . while exemplary embodiments of the present invention have been shown in the drawings and described above , it will be apparent to one skilled in the art that various embodiments of the present invention are possible . for example , the specific sequence of steps described above in fig1 , 4 a and 4 b , as well as the particular files and directories shown in fig2 should not be construed as limited to the specific embodiments described herein . modification may be made to these and other specific elements of the invention without departing from its spirit and scope as expressed in the following claims .