Abstract: Converting a first format program application, into a second format, which can be presented using a device type for which it wasn't designed. Examining the first format for commands that change screen state, and determining instructions in the second format with similar effect. First, searching the object-code calls that write to the screen, and for each determining those parameters that define outputs in a source human language, which can be altered to a target human language. Suggestions from the programmer can determine such output calls, or which parameters control elements of the source human language, to instead select element of the target human language. Alternatively, second, when the program is organized in a known format, searching for calls to output in the source human language, examining the object-code for parameters that define that output, and altering the program to output in a target human language.

Abstract: Modifying or replacing application program portions, from a first format to a second format, each of which makes substantially similar screen presentations, but with a different device or environment. The program instructions might have originally been developed for use with a particular mobile device or Operating System (OS). Once modified, the app can be used with some other device or OS, with substantially similar functions. The app could be modified to have outputs and inputs in a different human language. The app could alternatively be modified to allow a translator to observe, and possibly modify, the outputs and inputs to be in a different human language.

Abstract: A computer implemented method of conducting commerce over the Internet wherein a customer uses a client machine to request a web page through the Internet and a web server receives the request and sends a web page in hypertext mark up language (HTML) format that presents the customer with a form. The customer then enters information regarding a transaction at a web store. The form is set up so that the form values, i.e., the name of each variable, implies a way to store the variable's data in a database located in a web server. The forms data is processed into extensible markup language (XML) objects. By using XML path information in the HTML form variable names, the server is able to convert the HTML input into XML objects. This methodology allows the addition of any input fields without having to modify the code or programs residing on the server to accommodate these changes.