Patent Grant
9690549
The present disclosure relates to computer methods and systems, and more specifically, to methods of translating text of Graphical User Interface (GUI) screens and related computer program products and systems.
A software product may be developed in a first language (e.g., English), and then translated into a second language for use/sale in another country. The development of a version of the software product for a second language may be referred to as a localization build, and the version of the software product for the second language may be referred to as a localization version of the software product. For each Graphical User Interface (GUI) screen, fields may be provided for text strings, and the text strings of the first language used to populate these text fields of the GUI screens for the software product may be separately provided in a first resource file for the first language. Other resource files may thus be provided with text strings in other languages to provide localization versions of the software product in other languages using the GUI screens.
Currently, translators (also referred to as linguists) may translate individual text strings of the first resource file for the software product to a second language using a text editor without knowing where/how the text strings appear in real GUI screens of the software product. Without knowing the context of the text strings in GUI screens of the software product, however, a quality of the translation may be relatively low.
To provide a sufficient quality of translation, the build development cycle for a localization version of a software product may be complicated. For example, a linguist may translate the text strings from the first language to the second language, and then the software developer may make a first localization version of the software product in the second language using the text string translations provided by the linguist. A Quality Assurance (QA) function may then generate GUI screens of the software product from the first localization version and provide these screenshots to the linguist. Using these GUI screens, the linguist can check the quality of the translation in the context of the GUI screens and provide corrections/revisions using the text editor. The software developer can revise the localization versions of the software product based on these corrections/revisions, and the Quality Assurance (QA) function can verify the new translation delays in the product GUIs of the localization build of the software product.
This multi-step process of translation, however, may be complicated, and/or may increase time/delay to provide a localization build of a software product.
According to one aspect of the present disclosure, a method supporting editing of a software product may include obtaining a graphical user interface (GUI) screen for the software product, wherein the GUI screen includes a plurality of text fields, and wherein a first resource file includes text strings for respective ones of the text fields. A text mapping file may be generated for the software product, wherein the text mapping file includes a module for each text string of the first resource file, and wherein the module for each text string includes a text string from the resource file and a unique text string identification for the text string. A first screenshot of the GUI screen may be provided for display wherein the first screenshot includes a first text field with an original first text string for the GUI screen from a respective first module of the text mapping file and a second text field with an original second text string for the GUI screen from a respective second module of the text mapping file. User input of a new first text string may be received for the first text field. Responsive to receiving user input of the new first text string, the first module of the text mapping file may be updated to replace the original first text string of the first text field for the GUI screen with the new first text string of the first text field for the GUI screen. Responsive to receiving user input of the new first text string, a second screenshot of the GUI screen may be provided for display wherein the second screenshot includes the first text field with the new first text string from first module of the text mapping file and the second text field with the original second text string for the GUI screen from the second module of the text mapping file. A second resource file may be provided including the new first text string for the first text field of the GUI screen.
According to still another aspect of the present disclosure, a translation server may include a processor circuit. The processor circuit may be to obtain a graphical user interface screen for a software product, wherein the GUI screen includes a plurality of text fields, and wherein a first resource file includes text strings for respective ones of the text fields. The processor circuit may be to generate a text mapping file for the software product, wherein the text mapping file includes a module for each text string of the first resource file, wherein the module for each text string includes a text string from the resource file and a unique text string identification for the text string. The processor circuit may be to provide a first screenshot of the GUI screen for display wherein the first screenshot includes a first text field with an original first text string for the GUI screen from a respective first module of the text mapping file and a second text field with an original second text string for the GUI screen from a respective second module of the text mapping file. The processor circuit may be to receive user input of a new first text string for the first text field. The processor circuit may be to update the first module of the text mapping file to replace the original first text string of the first text field for the GUI screen with the new first text string of the first text field for the GUI screen responsive to receiving user input of the new first text string. The processor circuit may be to provide a second screenshot of the GUI screen for display wherein the second screenshot includes the first text field with the new first text string from first module of the text mapping file and the second text field with the original second text string for the GUI screen from the second module of the text mapping file responsive to receiving user input of the new first text string. The processor circuit may be to generate a second resource file including the new first text string for the first text field of the GUI screen.
According to still another aspect of the present disclosure, a computer program product may support editing of a software product, and the computer program product may include a computer readable storage medium comprising computer readable program code embodied therein. The computer readable program code may include computer readable program code to obtain graphical user interface (GUI) screen for the software product, wherein the GUI screen includes a plurality of text fields, and wherein a first resource file includes text strings for respective ones of the text fields. The computer readable program code may include computer readable program code to generate a text mapping file for the software product, wherein the text mapping file includes a module for each text string of the first resource file, wherein the module for each text string includes a text string from the resource file and a unique text string identification for the text string. The computer readable program code may include computer readable program code to provide a first screenshot of the GUI screen wherein the first screenshot includes a first text field with an original first text string for the GUI screen from a respective first module of the text mapping file and a second text field with an original second text string for the GUI screen from a respective second module of the text mapping file. The computer readable program code may include computer readable program code to receive user input of a new first text string for the first text field. The computer readable program code may include computer readable program code to update the first module of the text mapping file to replace the original first text string of the first text field for the GUI screen with the new first text string of the first text field for the GUI screen; responsive to receiving user input of the new first text string. The computer readable program code may include computer readable program code to provide a second screenshot of the GUI screen for display wherein the second screenshot includes the first text field with the new first text string from first module of the text mapping file and the second text field with the original second text string for the GUI screen from the second module of the text mapping file responsive to receiving user input of the new first text string. The computer readable program code may include computer readable program code to provide a second resource file including the new first text string for the first text field of the GUI screen.
Aspects of the present disclosure are illustrated by way of example and are not limited by the accompanying figures with like references indicating like elements.
Embodiments of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. Other embodiments may take many different forms and should not be construed as limited to the embodiments set forth herein. Like numbers refer to like elements throughout.
Current techniques to translate GUI screens of a software product may be inefficient, in part because, the linguist may be unable to see the real product graphical user interface when translating individual text strings. Efficiency may be improved, as discussed in greater detail below, by providing editing from product screens thereby improving a quality of translations and/or efficiency of providing a localization build of a software product.
According to embodiments disclosed herein, screenshots of graphical user interface (GUI) screens of a software product may be provided through an editor workstation to a translator (also referred to as a linguist or a user of the editor workstation) in substantially real-time as translations are entered so that all text strings of a GUI screen in the first language are provided to the translator at the same time and in the context of the particular screen, and so that translations of particular text strings are shown in the context of the particular screen as the text string translations are entered. By providing the context of each GUI screen and all text strings therein, the translator may provide a higher quality of translation of each GUI screen. According to some embodiments, a translation of each text string may be provided on the GUI screen as the translation is entered (and before a translation of another string on the same GUI screen is entered). By providing the translations in actual GUI screenshots as the translator enters translations of each text field, the translator can more efficiently correct/improve translations as needed (without waiting for someone else to enter the translations and generate screenshots after entering all revisions).
As further shown in
Translation server 105 (also referred to as a translation bot server or a translation bot) may work closely with editor workstation 101 and product server 109. Translation server 105 can open multiple browsers in a remote machine/machines (e.g., multiple browsers in remote product server 109 to access multiple product GUI screens of a software product). Translation server 105 may operate using an XML driven application, and web browsers may provide access to product GUI screens using instructions in an XML file. Such an XML file may be used to define project metadata used by translation server 105 and editor workstation 101, and to drive translation server 105 to retrieve GUI screens of a software product from product server 109.
Editor workstation 101 may be used by the translator (also referred to as a linguist, an editor workstation user, or a user) as an interface to translate GUI screens of a software product by invoking the translation server 105 to capture all GUI screens of the software product from product server 109. Responsive to translator/user input requesting a software product at block 401 of
Editor workstation 101 may display a list of GUI screens (see
As shown in
As indicated with dotted lines (that may be omitted in the actual screenshot), each text field 711, 715, and 717 may be defined for a respective area (e.g., a rectangle) of the screenshot within which pointer 701 (e.g., controlled using a pointer device such as a computer mouse) can be used to select the respective text field. More particularly, each text field may be defined by a respective module of a text mapping file generated by translation server 105.
As further shown, the screenshot that is provided to the translator/user on display 203 may include the text strings in the respective text fields with the respective unique text string identifications appended thereto. This is different than the respective product GUI screens where only the text strings would be provided.
In text mapping file modules according to some embodiments of inventive concepts, the screen ID field identifies the GUI screen to which the text mapping file module belongs, the text field provides the text string and a respective unique text string identification of the text field, and the coordinate/dimension information defines a location/size of the text field on the screen. Each text mapping file module can thus be used to specifically identify each text string/field using the respective unique text string identification, even if the same text is used in different text fields of the same GUI screen or different GUI screens of the software product. Accordingly, a unique translation may be provided for each text field, even when two text fields of the original text mapping file include the same text string in the first language. When performing a translation, for example, the same word/phrase in one language may have different translations in another language depending on the context of use.
The “Text” field of a text mapping file module may initially identify the English text string before translation, but after translation of the text string, the “Text” field may identify the text string of the translation. Editor program 215 of editor workstation 101 may run only as a pseudo product server, so when mapping text, editor program 215 may only be able to obtain the pseudo text strings from the text mapping file modules.
The “Coordinate” for each text mapping file module may define a top-left coordinate of the text field, which may be a rectangular area of the screen. Each text item (such as a label, text field, button, list, or image of a web page) may have its own area (e.g., a rectangle) on the screen (also referred to as a container). The “Dimension” for each text mapping file may define a size of the area of the text field (e.g., the height and width of a rectangular area). The coordinate and dimension information may be defined as pixel coordinates, as measurement coordinates, etc. When the translator wishes to translate one English string, the translator may click the area of the screen defined by the coordinate/dimension information of the text mapping file (indicated with dashed lines in FIG. 7) to select that English string, and responsive to that selection, editor workstation 101 may allow entry of the translation, e.g., by providing a prompt 721 for text entry as shown in
The initial build (in the first language, e.g., English) of the software product may be installed on product server 109, and the initial build of the software product may be available to translation server 105 over network(s) 115. Moreover, translation server 105 may access the software product at product server 109 using an XML metadata file as discussed above. An XML metadata file for a software product may allow translation server processor 307 to automatically capture each possible GUI screen (including each possible page, dropdown menu, text box, etc.) for which translation may be required.
Operations of translation server processor 307 are illustrated in the flow chart of
At blocks 505, processor 307 may generate a list of GUI screens of the software product, and at block 507, processor 307 may provide the list of screens for display at editor workstation 101 (e.g., as shown in
According to some embodiments, processor 307 of translation server 109 may obtain real-time software product GUI screens by accessing the software product through network interface 309 and network(s) 115 from product server 109. Responsive to user selection of a GUI screen (e.g., using the list of
Once a screenshot has been uploaded to editor workstation 101 through network 115 and network interface 209 at block 515, processor 207 may provide the screen (through device interface 202) on display 203 as shown in
Responsive to receiving the translation of the text string at block 517, processor 307 may update the text mapping file module for the text string at block 519 as shown, for example, in
Processor 307 of translation server 105 may thus use the updated text mapping file (including the updated module) to provide (e.g., upload) an updated screenshot of the GUI screen with the translation (through network interface 309 and network(s) 115) to editor workstation 101. Processor 207 may receive the updated screenshot 705d (shown in
Operations discussed above with respect to
When processor 307 of translation server 105 accesses a GUI screen of the software product at product server 109 (through network interface 309 and network(s) 115), processor 307 may capture the GUI screen and record all text strings of the screen and respective coordinate/dimension information in the text mapping file. This text mapping file, for example, may include a respective module for each text string/field of the software product as illustrated in
Operations of editor workstation 101 will now be discussed with reference to the flow chart of
A translator (also referred to as a user) may initiate operation of editor workstation 101 via input through an input user device 205, such as a keyboard and/or a pointing device (e.g., a computer mouse, a touch pad, a touch sensitive display, a track ball, etc.). For example, the translator may enter a name/identification of a software product using a keypad, and/or the translator may select a software product using a pointing device with a listing of software products on a GUI screen on display 203. Responsive to such user input requesting a software product at block 401, processor 207 may transmit a request for the software product for translation (through network interface 209 and network 115) at block 402 to translation server 105.
At block 403, processor 207 may receive the list of GUI screens for the software product (through network 115 and network interface 209) from translation server 105 (see block 507 of
At block 407, processor 207 may wait for user selection of a GUI screen from the list of
As shown in Figure
At block 415, processor 207 may accept user input through the input interface 204 from an input device to select text field 711 including the text “Password” of the selected product screen of
At block 419, processor 207/307 may accept user input of new text (e.g., a translation) for the first text field 711 through the input interface 204 from a user input device such as a keyboard. An example of such user input is illustrated in
At block 425, processor 207 may receive an update of the screenshot with the translation from translation server 105 as shown in
Once the screen has been updated with a translation of a text field as shown in
Responsive to not closing the current screen and not ending the session at blocks 429 and 431, processor 207/307 may accept user input selecting a new text field at block 415. As shown in
An example of such user input is illustrated in
At block 425, processor 207 may obtain an update of the screenshot with the translation from translation server 105 as shown in
Once the screenshot has been updated with translations of text fields 711 and 717 as shown in
If the translator returns to the list of GUI screens of
Operations of translation server 105 according to some embodiments will now be discussed with reference to the flow chart of
As discussed above, translation server 105 may be coupled with product server 109 and editor workstation 101 through one or more networks 115. Responsive to receiving a request for a software product from editor workstation 101 (through network(s) 115 and network interface 309) at block 501 (see block 402 of
At block 503, processor 307 may assign a unique text string identification (e.g., 02aq, 03br, 04cs, etc.) to each test string of the resource file for the software product, and at block 504, processor 307 may generate a text mapping file including a module for each text field of the resource file. As shown in
At block 505, processor 307 may provide a list of the GUI screens, and at block 507, processor 505 may transmit the list of GUI screens through network interface 309 and network(s) 115 to remote editor workstation 101. As discussed above, the list of GUI screens may include information allowing editor workstation 101 to generate the list of GUI screen names of
Processor 307 may then receive selection of one of the product screens through network interface 309 and network(s) 115 from remote editor workstation 101 at block 509 (see block 407 of
At block 517, processor 307 may receive the new text for one of the text fields (e.g., the first text field), and at block 519, processor 307 may update the respective module of the text mapping file with the new text. Referring to
Processor 307 may repeat operations of blocks 517, 519, 520, 521, and 523 for each of the text fields of the screenshot (corresponding to the selected GUI screen) any number of times until either the session ends at block 521 (e.g., responsive to an instruction/notification from editor workstation that the session has ended) or the selected screenshot has been closed at block 523 (e.g., responsive to an instruction/notification from editor workstation 101 that the selected screen has been closed). Processor 307 may repeat operations of blocks 507, 509, 515, 517, 519, 520, 521, and 523 for each of the GUI screens of the software product (included in the list of block 507) any number of times until the session ends at block 521.
When the session is ended at block 521, all text string translations (also referred to as new text) that have been entered will be saved in the respective modules of the text mapping file for the software product. Using the text string identifications in the respective modules, processor 307 can use the text mapping file to generate a new resource file (e.g., a new i18n resource file) for the software product including the new text strings at block 525. Like the original resource file for the software product, the new resource file may not include the text string identifications of the text mapping file. Accordingly, GUI screens generated using the new resource file will not include the text string identifications appended to the respective text strings as shown in the screenshots of
By assigning the text string identifications, providing the text mapping file with modules including the text string identifications, and appending the text string identifications to the screenshots used for translation, each text string can be uniquely identified by the translator even when two different text fields (of the same or different GUI screens) include the same text string. Accordingly, the translator may more easily provide different translations of the same text string in different text fields where the context may be different. The text string identifications may further facilitate generation of the new resource file.
According to some embodiments, metadata (e.g., an XML metadata file) may be provided for the software product being translated, with the metadata identifying each GUI screen of the software product. Translation server processor 307 may thus use the metadata to obtain each GUI screen of the software product at block 502 of
Example of XML metadata file:
The Elements attributes are XPath expressions which may be defined in the element_libraray.xml as follows:
In addition, the usage, tag name may be defined as “action”, and some pattern may be used to manipulate not only one element at one time:
According to some embodiments disclosed herein, processor 307 may use the software product metadata (e.g., XML metadata) to drive a web browser (e.g., browser program 331 of
As will be appreciated by one skilled in the art, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or contexts including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely as hardware, entirely as software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.
Any combination of one or more computer readable media may be utilized. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatuses (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be stored in memory and provided to a processor (also referred to as a processor circuit) of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various aspects of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.
The corresponding structures, materials, acts, and equivalents of any means or step plus function elements in the claims below are intended to include any disclosed structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The aspects of the disclosure herein were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure with various modifications as are suited to the particular use contemplated.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5678039 | Hinks | Oct 1997 | A |
| 5734907 | Jarossay | Mar 1998 | A |
| 5930809 | Middlebrook | Jul 1999 | A |
| 5991534 | Hamilton | Nov 1999 | A |
| 6580440 | Wagner | Jun 2003 | B1 |
| 6763517 | Hines | Jul 2004 | B2 |
| 6802055 | Jade | Oct 2004 | B2 |
| 6825859 | Severenuk | Nov 2004 | B1 |
| 6951012 | McGeorge, Jr. | Sep 2005 | B2 |
| 7191405 | Jaramillo | Mar 2007 | B1 |
| 7426716 | Kung | Sep 2008 | B2 |
| 7447624 | Fuhrmann | Nov 2008 | B2 |
| 7613789 | Cacenco | Nov 2009 | B2 |
| 7860846 | Takahashi | Dec 2010 | B2 |
| 7861226 | Episkopos | Dec 2010 | B1 |
| 7954090 | Qureshi | May 2011 | B1 |
| 7979850 | Ivanov | Jul 2011 | B2 |
| 7992129 | Chandhoke | Aug 2011 | B2 |
| 8037453 | Zawadzki | Oct 2011 | B1 |
| 8122436 | Costa | Feb 2012 | B2 |
| 8166462 | Kosche | Apr 2012 | B2 |
| 8302072 | Chandhoke | Oct 2012 | B2 |
| 8359582 | Elliott | Jan 2013 | B2 |
| 8370812 | Feblowitz | Feb 2013 | B2 |
| 8468502 | Lui | Jun 2013 | B2 |
| 8473899 | Centonze | Jun 2013 | B2 |
| 8499286 | Lawrance | Jul 2013 | B2 |
| 8510709 | Bordelon | Aug 2013 | B2 |
| 8627287 | Fanning | Jan 2014 | B2 |
| 8739128 | Cohen | May 2014 | B1 |
| 8893087 | Maddela | Nov 2014 | B2 |
| 20020123984 | Prakash | Sep 2002 | A1 |
| 20020129333 | Chandhoke | Sep 2002 | A1 |
| 20030001854 | Jade | Jan 2003 | A1 |
| 20030090453 | Fischer | May 2003 | A1 |
| 20030126559 | Fuhrmann | Jul 2003 | A1 |
| 20040046787 | Henry | Mar 2004 | A1 |
| 20040056894 | Zaika | Mar 2004 | A1 |
| 20040158451 | Mussini | Aug 2004 | A1 |
| 20040205713 | Keim | Oct 2004 | A1 |
| 20060150149 | Chandhoke | Jul 2006 | A1 |
| 20060173840 | Shaath | Aug 2006 | A1 |
| 20060253834 | Cacenco | Nov 2006 | A1 |
| 20080222190 | Kosaka | Sep 2008 | A1 |
| 20080250398 | Takahashi | Oct 2008 | A1 |
| 20100042972 | Cacenco | Feb 2010 | A1 |
| 20110119605 | Jayadevan | May 2011 | A1 |
| 20130055147 | Vasudev | Feb 2013 | A1 |
| 20140258971 | Jayadevan | Sep 2014 | A1 |
| 20160034436 | Peterson | Feb 2016 | A1 |
| Entry |
|---|
| W3C Architecture Domain Internationalization, FAQ: Localization vs. Internationalization, pulished by W3C before 2007, pp. 1-2. |
| Wikipedia, online encyclopedia, “XPath”, Definition from Wikipedia.org. Retrieved Mar. 17, 2015 from http://en.wikipedia.or/wiki/XPath . 9 pp. |
| Markus, “Why is WYSIWYG important for software localization?”, The Localization Tool, Apr. 24, 2007 [Online] retrieved Mar. 3, 2015 from http://www.the-localization-tool.com/why-is-wysiwyg-important-for-software-localizaton/ , 7 pp. |
| Kumar, Ravikant, “Globalization, Internationalization (I18N), and Localization using C# and .NET 2.0”, Code Project, Bangalore India, Nov. 2, 2009 [Online] retrieved Mar. 15, 2015 from http://www.codeproject.com/Articles/43360/Globalization-Internationalization-I-N-and-Localization.com , 9 pp. |
| “Walkthrough: Using Resources for Localization with ASP.NET”, Microsoft Developer Network, [Online] retrieved Mar. 14, 2015 from https://msdn.microsoft.com/en-us/library/fw69ke6f(v=vs.140).aspx , 5 pp. |
| “How to: Create a Localized Version of a Resource File”, Microsoft Virtual Studio 2010, [Online] retrieved Mar. 14, 2015 from https://msdn.microsoft.com/en-us/library/vstudio/aa992030(v=vs.100).aspx , 1 pp. |
| Localization Seminar—Professional Development for Translators & Interpreters, American Translators Association, An ATA Professional Development Event; Renaissance Seattle Hotel, Aug. 23-24, 2008, Seattle, Washington, [Online] retrieved Mar. 3, 2015 from http://www.atanet.org/pd/localization/abstracts.htm , 3 pp. |
| Number | Date | Country | |
|---|---|---|---|
| 20160283204 A1 | Sep 2016 | US |
