Abstract: File selection techniques that can handle overlapping module contexts provide flexible and reversible backup, restore, migration, deployment and synchronization operations. Both remote (administrative) control and local (user) control of the file selection are provided. Application and configuration specific templates are provided to a user from the remote administrator for further customization by selecting or de-selecting configurations, applications and/or individual files or configuration entries. The templates may be controlled geographically by the IP address or identity associated with the user. A user's interaction with the customization is saved and the order of changes is maintained, so that when the templates are updated, the user's customizations can be re-applied. The administrator may override user settings based on rules, which may also be geographically determined. The file selection may also be altered based on media type and location, e.g., local backup vs. server backup.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: Embodiments of the present invention provide an approach to automatically convert existing support materials (support manuals, troubleshooting guides, content, help files, etc.) into machine-executable programs so as to obviate for manual execution of the steps described in the support materials. That is, the embodiments of the invention will (among other things): create support-based programs that automate the execution of previously manual steps; create an inventory of said programs; parse existing support documentation; map sections of each support document into existing program automation; construct a sequence of program automations that resemble the flow of each support document; and/or associate a constructed sequence of automation with a support document that could be executed automatically.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: A method and system for validating translated files for inclusion in an application being developed. Translatable files having externalized content in a single base language are sent for translation into other languages. Translated files resulting from a translation of the translatable files are received. Each translated file is statically and dynamically validated to detect error(s). The static validation is based on comparing the translatable files to the translated files. The dynamic validation is based on a simulation of how a user interface of the application presents the externalized content, without including an actual presentation of the externalized content by the user interface. Modified translated files that correct the detected error(s) are received and provided for a presentation of the externalized content by the user interface.

Abstract: File selection techniques that can handle overlapping module contexts provide flexible and reversible backup, restore, migration, deployment and synchronization operations. Both remote (administrative) control and local (user) control of the file selection are provided. Application and configuration specific templates are provided to a user from the remote administrator for further customization by selecting or de-selecting configurations, applications and/or individual files or configuration entries. The templates may be controlled geographically by the IP address or identity associated with the user. A user's interaction with the customization is saved and the order of changes is maintained, so that when the templates are updated, the user's customizations can be re-applied. The administrator may override user settings based on rules, which may also be geographically determined. The file selection may also be altered based on media type and location, e.g., local backup vs. server backup.

Abstract: Embodiments of the present invention provide an approach to automatically convert existing support materials (support manuals, troubleshooting guides, content, help files, etc.) into machine-executable programs so as to obviate for manual execution of the steps described in the support materials. That is, the embodiments of the invention will (among other things): create support-based programs that automate the execution of previously manual steps; create an inventory of said programs; parse existing support documentation; map sections of each support document into existing program automation; construct a sequence of program automations that resemble the flow of each support document; and/or associate a constructed sequence of automation with a support document that could be executed automatically.

Abstract: A method and system for validating translated files for inclusion in an application being developed. Translatable files having externalized content in a single base language are sent for translation into other languages. Translated files resulting from a translation of the translatable files are received. Each translated file is statically and dynamically validated to detect error(s). The static validation is based on comparing the translatable files to the translated files. The dynamic validation is based on a simulation of how a user interface of the application presents the externalized content, without including an actual presentation of the externalized content by the user interface. Modified translated files that correct the detected error(s) are received and provided for a presentation of the externalized content by the user interface.

Abstract: File selection techniques that can handle overlapping module contexts provide flexible and reversible backup, restore, migration, deployment and synchronization operations. Both remote (administrative) control and local (user) control of the file selection are provided. Application and configuration specific templates are provided to a user from the remote administrator for further customization by selecting or de-selecting configurations, applications and/or individual files or configuration entries. The templates may be controlled geographically by the IP address or identity associated with the user. A user's interaction with the customization is saved and the order of changes is maintained, so that when the templates are updated, the user's customizations can be re-applied. The administrator may override user settings based on rules, which may also be geographically determined. The file selection may also be altered based on media type and location, e.g., local backup vs. server backup.

Abstract: A replica image of a computer system is loaded to a target computer system being built. A detection program running on the target computer system detects configuration information and attached devices and provides this information to a build program. The build program provides needed program components, applications, prerequisites and device drivers for the target computer according to build rules defined for the target computer type/model. Optionally, the detection program further detects that there are updates required for the detection program and installs the updates before proceeding with the build process.

Abstract: A replica (clone) image of a computer system comprising an operating system is created. The clone image is loaded at a second computer system. A characteristic (such as computer type or model) of the second computer system is used to select a list of components such as device drivers appropriate for the second computer system. Components needed for the second computer system are found using the component list.