Method and system for translation management of source language text phrases

RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. §120 of U.S. patent application Ser. No. 09/864,120 filed May 24, 2001, now issued as U.S. Pat. No. 7,283,947, as a continuation application.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to the translation of text phrases from a source language to a target language. The present invention specifically relates to a management of such a translation that facilitates an effective operation of a source code control system.

2. Description of the Related Art

Software developers utilize some form of a source code control system for organizing, tracking, and maintaining an evolving source code configuration of a national language support (NLS) application. Each text phrase (e.g., “File”, “Edit”, “View”, “Insert”, “Format”, “Tools”, “Table”, “Window” and “Help” on a toolbar of a word processing NLS application) in a source language (hereinafter “source language text phrase”) is extracted from the source code and placed within an external master text file which serves as a basis for multiple translation of the source language text phrases therein. While known source code control systems can perform a comprehensive management of the source code configuration, the prior art source code control systems typically fail to perform a comprehensive management of the master text file during various translation of the source language text phrases therein.

Specifically, such systems often fail to address several issues. The first issue is a modification of a source language text phrase within the master text file while minimizing, if not preventing, inadvertent overwrites and corruption of other source language text phrases within the master text file. The second issue is an importation management of a translated text file that provides a notification of the translated text file being an incomplete translation of the master text file. The third issue is an importation management of a translated version of a source language text phrase (hereinafter “target language text phrase”) being a translation of an incorrect version of the source language text phrase. The present invention addresses these issues.

SUMMARY OF THE INVENTION

The present invention relates to a method and a system for translation management of master text files that overcomes the disadvantages associated with the prior art. Various aspects of the invention are novel, non-obvious, and provide various advantages. While the actual nature of the present invention covered herein can only be determined with reference to the claims appended hereto, certain features, which are characteristic of the embodiments disclosed herein, are described briefly as follows.

One form of the present invention is a method for managing a translation of a master text file. A first source language text phrase is stored as a first entry within a database. A target language text phrase as a translated version of the first source language text phrase is stored within the database after a storage of the first source language text phrase within the database. A second source language text phrase as a modified version of the first source language text phrase is stored within the database after a storage of the first source language text phrase within the database. A notification indicating the target language text phrase is an incorrect translation is communicated when the second source language text phrase is stored within the database after a storage of the target language text phrase within the database.

A second form of the present invention is a method for managing a master text file including a source language text phrase. The source language text phrase is stored as a first entry within a database. A translated text file corresponding to the master text file is imported. The translated text file includes one or more target language text phrases. Each target language text phrase is stored as an individual entry within the database. A notification indicating the translated text file is an incomplete translation of the master text file is communicated when all of the target language text phrases fail to correspond to the source language text phrase.

A third form of the present invention is a system for managing a translation of a master text file. The system comprises a database and a computer. The computer is operable to control a storage of a first source language text phrase is stored as a first entry within a database; a storage of a target language text phrase as a translated version of the first source language text phrase within the database after a storage of the first source language text phrase within the database; and a storage of a second source language text phrase as a modified version of the first source language text phrase within the database after a storage of the first source language text phrase within the database. The computer is further operable to communicate a notification indicating the target language text phrase is an incorrect translation when the second source language text phrase is stored within the database after a storage of the target language text phrase within the database.

A fourth form of the present invention is a system for managing a master text file including a source language text phrase. The system comprises a database and a computer. The computer is operable to control a storage of the source language text phrase as a first entry within a database; an importation of translated text file corresponding to the master text file, the translated text file including one or more target language text phrases; and a storage of each target language text phrase as an individual entry within the database. The computer is further operable to communicate a notification indicating the translated text file is an incomplete translation of the master text file when all of the target language text phrases fail to correspond to the source language text phrase.

A fifth form of the present invention is a computer program product in a computer readable medium for managing a translation of a master text file. The computer program product comprises computer readable code for storing a first source language text phrase is stored as a first entry within a database; a target language text phrase as a translated version of the first source language text phrase within the database after a storage of the first source language text phrase within the database; and a second source language text phrase as a modified version of the first source language text phrase within the database after a storage of the first source language text phrase within the database. The computer program product further comprises computer readable code for communicating a notification indicating the target language text phrase is an incorrect translation when the second source language text phrase is stored within the database after a storage of the target language text phrase within the database.

A sixth form of the present invention is a computer program product in a computer readable medium for managing a master text file including a source language text phrase. The computer program product comprises computer readable code for storing the source language text phrase as a first entry within a database; importing a translated text file corresponding to the master text file, the translated text file including one or more target language text phrases; and storing each target language text phrase as an individual entry within the database. The computer program product further comprises computer readable code for communicating a notification indicating the translated text file is an incomplete translation of the master text file when all of the target language text phrases fail to correspond to the source language text phrase.

The foregoing forms and other forms, features and advantages of the present invention will become further apparent from the following detailed description of the presently preferred embodiments, read in conjunction with the accompanying drawings. The detailed description and drawings are merely illustrative of the invention rather than limiting, the scope of the invention being defined by the appended claims and equivalents thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of one embodiment of computer hardware employed in the present invention;

<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram of one embodiment of computer software employed in the <figref idrefs="DRAWINGS">FIG. 1</figref> computer hardware;

<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow chart of one embodiment in accordance with the present invention of a master text file storage routine implemented by the <figref idrefs="DRAWINGS">FIG. 2</figref> computer software;

<figref idrefs="DRAWINGS">FIG. 4</figref> is a flow chart of one embodiment in accordance with the present invention of a translated text file storage routine implemented by the <figref idrefs="DRAWINGS">FIG. 2</figref> computer software;

<figref idrefs="DRAWINGS">FIG. 5</figref> is a flow chart of one embodiment in accordance with the present invention of a source language text phrase modification routine implemented by the <figref idrefs="DRAWINGS">FIG. 2</figref> computer software;

<figref idrefs="DRAWINGS">FIG. 6</figref> is a flow chart of one embodiment in accordance with the present invention of an incomplete translation notification routine implemented by the <figref idrefs="DRAWINGS">FIG. 2</figref> computer software; and

<figref idrefs="DRAWINGS">FIG. 7</figref> is a flow chart of one embodiment in accordance with the present invention of an incorrect translation notification routine implemented by the <figref idrefs="DRAWINGS">FIG. 2</figref> computer software.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS

A computer <b>10</b> of the present invention is shown in <figref idrefs="DRAWINGS">FIG. 1</figref>. Referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, computer <b>10</b> may be configured in any form for accepting structured inputs, processing the inputs in accordance with prescribed rules, and outputting the processing results as would occur to those having ordinary skill in the art, such as, for example, a personal computer, a workstation, a super computer, a mainframe computer, a minicomputer, a super minicomputer, and a microcomputer. Preferably, as shown, computer <b>10</b> is a server including a bus <b>11</b> for facilitating electrical communication among one or more central processing units (CPU) <b>12</b>, a read-only memory (ROM) <b>13</b>, a random access memory (RAM) <b>14</b>, an input/output (I/O) controller <b>15</b>, a disk controller <b>16</b>, a communication controller <b>17</b>, and a user interface controller <b>18</b>.

CPU <b>12</b> is preferably one of the Intel families of microprocessors, one of the AMD families of microprocessors, one of the Motorola families of microprocessors, or one of the various versions of a Reduced Instruction Set Computer microprocessor such as the PowerPC chip manufactured by International Business Machine Corporation (IBM). ROM <b>13</b> stores various controlling programs such as the Basic Input-Output System (BIOS) developed by IBM. RAM <b>14</b> is the memory for loading an operating system and selectively loading controlling programs and application programs.

Controller <b>15</b> is an aggregate of controllers for facilitating an interaction between CPU <b>12</b> and pointing devices such as a mouse <b>20</b> and a keyboard <b>21</b>, and between CPU <b>12</b> and output devices such as a printer <b>22</b> and a fax <b>23</b>. Controller <b>16</b> is an aggregate of controllers for facilitating an interaction between CPU <b>12</b> and data storage devices such as disks drives <b>24</b> in the form of a hard drive, a floppy drive, and a compact-disc drive. The hard drive of disk drives <b>24</b> stores a conventional operating system, such as an AIX operating system or an OS/2 operating system by IBM. Controller <b>17</b> is an aggregate of controllers for facilitating an interaction between CPU <b>12</b> and a network <b>25</b>, and between CPU <b>12</b> and a database <b>26</b> stored on a local or remote storage device. Controller <b>18</b> is an aggregate of controllers for facilitating an interaction between CPU <b>12</b> and a graphic display device such as a monitor <b>27</b>, and between CPU <b>12</b> and an audio device such as a speaker <b>28</b>.

Those having skill in the art will appreciate alternative computer hardware embodiments of computer <b>10</b> for implementing the principles of the present invention.

Referring additionally to <figref idrefs="DRAWINGS">FIG. 2</figref>, computer <b>10</b> includes translation management software <b>30</b> for implementing a master text file storage routine <b>40</b> (<figref idrefs="DRAWINGS">FIG. 3</figref>), a translated text file routine <b>50</b> (<figref idrefs="DRAWINGS">FIG. 4</figref>), a source language text phrase modification routine <b>60</b> (<figref idrefs="DRAWINGS">FIG. 5</figref>), an incomplete translation routine <b>70</b> (<figref idrefs="DRAWINGS">FIG. 6</figref>), and an incorrect translation routine <b>80</b> (<figref idrefs="DRAWINGS">FIG. 7</figref>) under control of the operating system. Software <b>30</b> is a computer program physically stored within a hard drive of disk drives <b>24</b> whereby the hard drive is a computer readable medium that is electrically, magnetically, optically, or chemically altered to store computer readable code. In other embodiments of computer <b>10</b>, software <b>30</b> can be stored in other computer readable mediums of computer <b>10</b>, such as the CD-ROM drive of disk drives <b>24</b>, or software <b>30</b> can be downloaded to computer <b>10</b> via network <b>25</b>. Also in other embodiments of computer <b>10</b>, software <b>30</b> can be partially or fully implemented with digital circuitry, analog circuitry, or both.

A functional description of software <b>30</b> will now be described herein by the description of data transfers and signal transmissions between software <b>30</b> and database <b>26</b> during execution of the various routines of the present invention. First, an implementation of routine <b>40</b> (<figref idrefs="DRAWINGS">FIG. 3</figref>) by a database management module <b>31</b> of software <b>30</b> to initially store a master text file MTF within database <b>26</b> is described. Master text file MTF includes multiple source language text phrases such as source language text phrase SLTP. Second, an implementation of routine <b>50</b> (<figref idrefs="DRAWINGS">FIG. 4</figref>) by database management module <b>31</b> to store a translated text file TTF within database <b>26</b> is described. Translated text file TTF includes multiple target language text phrases such as a target language text phrase TLTP that corresponds to source language text phrase SLTP.

Third, an implementation of routine <b>60</b> (<figref idrefs="DRAWINGS">FIG. 5</figref>) by database management module <b>31</b> to store a modified version SLTP′ of source language text phrase SLTP within database <b>26</b> is described. Fourth, an implementation of routine <b>70</b> (<figref idrefs="DRAWINGS">FIG. 6</figref>) by a verification notification module <b>32</b> of software <b>30</b> to generate a verification notification VN indicating an incomplete translation of master text file MTF by translated text file TTF is described. Finally, an implementation of routine <b>80</b> (<figref idrefs="DRAWINGS">FIG. 7</figref>) to generate a modification notification MN indicating an incorrect translation of source language text phrase SLTP by target language text phrase TLTP is described. Those having ordinary skill in the art will appreciate the physical elements of computer <b>10</b> that are associated with such data transfers and signal transmissions.

Referring to <figref idrefs="DRAWINGS">FIGS. 1-3</figref>, module <b>31</b> imports master text file MTF during a stage S<b>42</b> of routine <b>40</b> in response to appropriate commands (not shown) from a source code manager (not shown) via a user interface <b>34</b> of software <b>30</b> (e.g., a graphical user interface or a network interface). Module <b>31</b> thereafter proceeds to a stage S<b>44</b> of routine <b>40</b> to store each source language text phrase of master text file MTF as individual entries within database <b>26</b>. The following TABLE 1 illustrates one embodiment of a database table for each individual entry of a source language text phrase of master text file MTF:

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="6"><colspec colname="1" colwidth="21pt" align="center" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="35pt" align="center" /><colspec colname="4" colwidth="49pt" align="center" /><colspec colname="5" colwidth="56pt" align="center" /><colspec colname="6" colwidth="56pt" align="center" /><thead><row><entry namest="1" nameend="6" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="6" align="center" rowsep="1" /></row><row><entry /><entry>SOURCE</entry><entry /><entry /><entry /><entry /></row><row><entry /><entry>LANGUAGE</entry><entry>SOURCE</entry></row><row><entry>ROW</entry><entry>TEXT</entry><entry>ID.</entry><entry>SOURCE</entry><entry>VERIFICATION</entry><entry>MODIFICATION</entry></row><row><entry>NO.</entry><entry>PHRASE</entry><entry>NO.</entry><entry>TIMESTAMP</entry><entry>FLAG</entry><entry>FLAG</entry></row><row><entry namest="1" nameend="6" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>1</entry><entry>“FILE”</entry><entry>1</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>2</entry><entry>“EDIT”</entry><entry>2</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>3</entry><entry>“VIEW”</entry><entry>3</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>4</entry><entry>“INSERT”</entry><entry>4</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>5</entry><entry>“FORMAT”</entry><entry>5</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>6</entry><entry>“TOOLS”</entry><entry>6</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>7</entry><entry>“TABLE”</entry><entry>7</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>8</entry><entry>“WINDOW”</entry><entry>8</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry>9</entry><entry>“HELP”</entry><entry>9</entry><entry>Date/Time</entry><entry>Reset/Set</entry><entry>Reset/Set</entry></row><row><entry namest="1" nameend="6" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

The SOURCE ID NO. column includes data indicative of an identification number of each source language text phrase. The SOURCE TIMESTAMP column includes data indicative of a date and a time of an initial storage of a source language text phrase or a date and time of modified version of a source language text phrase as will be further described herein in connection with routine <b>60</b> (<figref idrefs="DRAWINGS">FIG. 5</figref>). The flags of the VERIFICATION FLAG column are initially reset and are selectively set as will be further described herein in connection with routine <b>70</b> (<figref idrefs="DRAWINGS">FIG. 6</figref>). The MODIFICATION FLAG column is initially reset and is selectively set as will be further described herein in connection with routine <b>80</b> (<figref idrefs="DRAWINGS">FIG. 7</figref>).

Module <b>31</b> thereafter proceeds to a stage S<b>46</b> of routine <b>40</b> to communicate the location of master text file MTF within database <b>26</b> (e.g., rows 1-9) to module <b>32</b> and module <b>33</b>. Routine <b>40</b> is terminated upon completion of stage S<b>46</b>.

Referring to <figref idrefs="DRAWINGS">FIGS. 1</figref>, <b>2</b>, and <b>4</b>, module <b>31</b> imports translated text file TTF during a stage S<b>52</b> of routine <b>50</b> in response to appropriate commands (not shown) from a source code manager (not shown) via user interface <b>34</b>. Module <b>31</b> thereafter proceeds to a stage S<b>54</b> of routine <b>50</b> to store each target language text phrase of translated text file TTF as individual entries within database <b>26</b>. The following TABLE 2 illustrates one embodiment of a database table for each individual entry of a target language text phrase of translated text file TTF:

<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="91pt" align="left" /><colspec colname="3" colwidth="42pt" align="center" /><colspec colname="4" colwidth="56pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 2</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>ROW</entry><entry>TARGET LANGUAGE</entry><entry>TARGET</entry><entry>TARGET</entry></row><row><entry>NO.</entry><entry>TEXT PHRASE</entry><entry>ID NO.</entry><entry>TIMESTAMP</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>10</entry><entry>Translation of “FILE”</entry><entry>1</entry><entry>Date/Time</entry></row><row><entry>11</entry><entry>Translation of “EDIT”</entry><entry>2</entry><entry>Date/Time</entry></row><row><entry>12</entry><entry>Translation of “VIEW”</entry><entry>3</entry><entry>Date/Time</entry></row><row><entry>13</entry><entry>Translation of “INSERT”</entry><entry>4</entry><entry>Date/Time</entry></row><row><entry>14</entry><entry>Translation of “FORMAT”</entry><entry>5</entry><entry>Date/Time</entry></row><row><entry>15</entry><entry>Translation of “TOOLS”</entry><entry>6</entry><entry>Date/Time</entry></row><row><entry>16</entry><entry>Translation of “TABLE”</entry><entry>7</entry><entry>Date/Time</entry></row><row><entry>17</entry><entry>Translation of “WINDOW”</entry><entry>8</entry><entry>Date/Time</entry></row><row><entry>18</entry><entry>Translation of “HELP”</entry><entry>9</entry><entry>Date/Time</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

The TARGET ID NO. includes data indicative of an identification number of a corresponding source language text phrase. The TIMESTAMP column includes data indicative of a date and a time of a storage of a target language text phrase. In an alternative embodiment, the TARGET TIMESTAMP column can be excluded from TABLE 2 and included within TABLE 1.

Module <b>31</b> thereafter proceeds to a stage S<b>56</b> of routine <b>50</b> to communicate the location of translated text file TTF within database <b>26</b> (e.g., rows 10-18) to module <b>32</b> and module <b>33</b>. Routine <b>50</b> is terminated upon completion of stage S<b>56</b>.

Referring to <figref idrefs="DRAWINGS">FIGS. 1</figref>, <b>2</b>, and <b>5</b>, module <b>31</b> imports a modified version SLTP′ of source language text phrase SLTP during a stage S<b>62</b> of routine <b>60</b> in response to appropriate commands (not shown) from a source code manager (not shown) via user interface <b>34</b>. Module <b>31</b> thereafter proceeds to a stage S<b>64</b> of routine <b>40</b> to store modified version SLTP′ of source language text phrase SLTP within database <b>26</b>. In one embodiment, module <b>31</b> overwrites source language text phrase SLTP with modified version SLTP′ and modifies the data under the SOURCE TIMESTAMP column to reflect the storage of the modified version SLTP′. Routine <b>60</b> is terminated upon completion of stage S<b>64</b>.

Referring to <figref idrefs="DRAWINGS">FIGS. 1</figref>, <b>2</b>, and <b>6</b>, module <b>32</b> verifies a storage of a target language text phrase for each source language text phrase within database <b>26</b> during a stage S<b>72</b> of routine <b>70</b> in response to appropriate commands (not shown) from a source code manager (not shown) via a user interface <b>34</b>. In one embodiment, module <b>32</b> compares the SOURCE ID NO. column of TABLE 1 and the TARGET ID NO. column of TABLE 2 to ascertain whether any target language text phrases are missing from translated text file TTF. Module <b>32</b> thereafter proceeds to a stage S<b>74</b> of routine <b>70</b> to direct module <b>31</b> to set the flags under the VERIFICATION FLAG column of TABLE 1 for each source language text phrase that does not have a corresponding target language text phrase stored within database <b>26</b>. For example, translated text file TTF may have excluded the target language text phrase of row 10 of TABLE 2 from database <b>26</b>. Thus, the flag for the source language text phrase of row 1 of TABLE 1 will be set.

Module <b>32</b> thereafter proceeds to a stage S<b>76</b> of routine <b>70</b> to direct module <b>31</b> to store each source language text phrase that does not have a corresponding target language text phrase stored within database <b>26</b> into translated text file TTF. For example, with the target language text phrase of row 10 of TABLE 2 missing from translated text file TTF, the source language text phrase of row 1 of TABLE 1 will be stored in row 10 of TABLE 2. Module <b>32</b> thereafter proceeds to a stage S<b>78</b> of routine <b>70</b> to communicate a verification notification VN to the source code manager (not shown) via user interface <b>34</b>. The verification notification VN will indicate incomplete translation of master text file MTF by translated text file TTF. Routine <b>70</b> is terminated upon completion of stage S<b>78</b>.

Referring to <figref idrefs="DRAWINGS">FIGS. 1</figref>, <b>2</b>, and <b>7</b>, module <b>33</b> compares the timestamps of each corresponding pair of source language text phrase and target language text phrase during a stage S<b>82</b> of routine <b>80</b> in response to appropriate commands (not shown) from a source code manager (not shown) via a user interface <b>34</b>. In one embodiment, module <b>33</b> compares the SOURCE TIMESTAMP column of TABLE 1 and the TARGET TIMESTAMP column of TABLE 2 to ascertain whether the correct version (original or modified) of each source language text phrase was translated. The TARGET TIMESTAMP including a date and a time that is prior to corresponding date and a time of the SOURCE TIMESTAMP is an indication that the target language text phrase is a translated version of an original version of a corresponding source language text phrase instead of being a translated version of a modified version of a corresponding source language text phrase.

Module <b>33</b> thereafter proceeds to a stage S<b>84</b> of routine <b>80</b> to direct module <b>31</b> to set the flags under the MODIFICATION FLAG column of TABLE 1 for each source language text phrase that was modified after a storage of a corresponding target language text phrase. For example, when target language text phrase TLTP was stored in database <b>26</b> prior to an importation and storage of the modified version STLP′ of source language text phrase SLTP, then the modification flag is set. Module <b>33</b> thereafter proceeds to a stage S<b>86</b> of routine <b>80</b> to direct module <b>31</b> to store each modified version of source language text phrases that have been incorrectly translated into the appropriate location of translated text file TTF. For example, the modified version STLP′ of source language text phrase SLTP is written within the database entry of target language text phrase TLTP. Module <b>32</b> thereafter proceeds to a stage S<b>78</b> of routine <b>70</b> to communicate a modification notification MN to the source code manager (not shown) via user interface <b>34</b>. The modification notification MN will indicate an incorrect translation of one or more target language text phrases. Routine <b>80</b> is terminated upon completion of stage S<b>88</b>.

While the embodiments of the present invention disclosed herein are presently considered to be preferred, various changes and modifications can be made without departing from the spirit and scope of the invention. The scope of the invention is indicated in the appended claims, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.