Abstract: A system, method, and non-transitory computer-readable media are provided for using a consumer-agnostic file to make and view changes to an interface that can be published for viewing by other users. A published version of the consumer-agnostic file may be accessed from a server. The consumer-agnostic file defines components of a customized user interface as identified among a structured set of keys. The keys are associated with corresponding interface regions and/or characteristics of the components. The components may be defined based on fields of a record, such as a record selected for view when the user interface is rendered. The user interface may allow switching between a configuration mode of the customized user interface where the customized user interface may be modified and a rendering mode of the customized user interface where the customized user interface may be viewed, optionally without re-accessing the published version of the consumer-agnostic file from the server.

Abstract: Text strings from computer-based applications are converted from multiple external formats into an internal format. The text strings are stored in a terminology database. Translations for the test strings are also stored in the terminology database and associated with the corresponding text strings. In one aspect, text strings are converted into a export format for translation into one or more target languages. The translations are converted into the appropriate external formats and output to the applications that supplied the text strings. In another aspect, the terminology database is queried for an appropriate translation for each newly converted text string. In still another aspect, metadata for the text strings is created and associated with the text strings in the terminology database, and used as query criteria to determine the appropriate translation. The metadata may be exported in conjunction with the text strings.

Abstract: Text strings from computer-based applications are converted from multiple external formats into an internal format. The text strings are stored in a terminology database. Translations for the test strings are also stored in the terminology database and associated with the corresponding text strings. In one aspect, text strings are converted into a export format for translation into one or more target languages. The translations are converted into the appropriate external formats and output to the applications that supplied the text strings. In another aspect, the terminology database is queried for an appropriate translation for each newly converted text string. In still another aspect, metadata for the text strings is created and associated with the text strings in the terminology database, and used as query criteria to determine the appropriate translation. The metadata may be exported in conjunction with the text strings.