Abstract: An air handling system includes a movable evaporative media section. The movable evaporative media section is movable between a closed position and an open position. When the movable evaporative media section is in an open position, the movable evaporative media section exposes an opening to the air flow and is positioned to allow at least a portion of the air flow in the volume to flow around the movable evaporative media section and through the opening.

Abstract: This application discloses a lighting emitting diode (LED) illumination system that operates at least in a boost mode and a bypass mode. The LED illumination system includes a plurality of LEDs and bypass elements. Each bypass element is coupled in parallel with one or more LEDs, and configured to bypass them selectively in the bypass mode. A boost converter is configured to drive the LEDs. The boost converter includes a boost controller that is configured to enable the boost mode in response to a boost enable signal. In the boost mode, the boost controller is electrically coupled to control the boost converter to drive the LEDs by a boosted drive voltage, and in the bypass mode, the boost controller is deactivated to allow the boost converter to drive a subset of the LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage.

Abstract: This application discloses a lighting emitting diode (LED) illumination system that operates at least in a boost mode and a bypass mode. The LED illumination system includes a plurality of LEDs and bypass elements. Each bypass element is coupled in parallel with one or more LEDs, and configured to bypass them selectively in the bypass mode. A boost converter is configured to drive the LEDs. The boost converter includes a boost controller that is configured to enable the boost mode in response to a boost enable signal. In the boost mode, the boost controller is electrically coupled to control the boost converter to drive the LEDs by a boosted drive voltage, and in the bypass mode, the boost controller is deactivated to allow the boost converter to drive a subset of the LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage.

Abstract: This application discloses a lighting emitting diode (LED) illumination system that operates at least in a boost mode and a bypass mode. The LED illumination system includes a plurality of LEDs and bypass elements. Each bypass element is coupled in parallel with one or more LEDs, and configured to bypass them selectively in the bypass mode. A boost converter is configured to drive the LEDs. The boost converter includes a boost controller that is configured to enable the boost mode in response to a boost enable signal. In the boost mode, the boost controller is electrically coupled to control the boost converter to drive the LEDs by a boosted drive voltage, and in the bypass mode, the boost controller is deactivated to allow the boost converter to drive a subset of the LEDs by a regular drive voltage that is substantially lower than the boosted drive voltage.

Abstract: Multilingual build integration for compiled applications is described in which support for application localization of compiled programming languages is provided as an integrated component of a development environment. Localizations integrate with application builds in the development environment so that updates are synchronized with project resources for multiple languages. This involves producing translation target files (e.g., localization files) for one or more selected languages by parsing and interpreting source files for the project to identify resources for translation. Localization files in the project that have been updated may be exposed in various ways for translation via the system, a translation service, or other translation source. Translated localization files are used to create dynamic resource files for the particular programming language that are compiled as part of the build process into language specific resource files.

Abstract: Integrated application localization techniques are described in which support for application localization is provided as an integrated component of a development environment. Localizations for selected languages/locales integrate with application builds in the development environment so that updates are synchronized with project resources for multiple languages. This involves creating and employing localization files corresponding to source content of a project using a designated file format suitable to enable translations. Localization files that are created in the designated format may be exposed in various ways for translation via the system, a developer, a translation service, or other selected translation sources. A single multilingual resource file for an application is then generated to contain resources in multiple languages based on translations made available through the translation sources.

Abstract: Electronic files for a localization project may be created and/or managed. The electronic files may be based on a data structure that defines the format and content of the electronic files and may include a first data structure portion that may contain data representing a plurality of references to localization project files. The data structure may includes a second data structure portion that may be associated with the first data structure portion that may contain data that may represent a plurality of references to standard files.

Abstract: Resource tracker techniques are described in which resource trackers may be generated, assigned to resources, and used to track resources throughout a development environment. The resource trackers may be configured in a designated format that is suitable to distinguish different resources one from one another. In one approach, resource trackers are derived as a combination of a user-supplied project identifier and defined resource identifiers. Resource trackers may be embedded into code defining corresponding resources and exposed to identify resources in connection with various development operations. In an embodiment, the resources trackers may be employed to provide visual indications of resources that appear within a user-interface for a project that is output for testing. A developer may identify resources based on resource trackers exposed via the user-interface and navigate back to underlying code in various ways to address any issues identified through the testing.

Abstract: Integrated application localization techniques are described in which support for application localization is provided as an integrated component of a development environment. Localizations for selected languages/locales integrate with application builds in the development environment so that updates are synchronized with project resources for multiple languages. This involves creating and employing localization files corresponding to source content of a project using a designated file format suitable to enable translations. Localization files that are created in the designated format may be exposed in various ways for translation via the system, a developer, a translation service, or other selected translation sources. A single multilingual resource file for an application is then generated to contain resources in multiple languages based on translations made available through the translation sources.

Abstract: Integrated application localization techniques are described in which support for application localization is provided as an integrated component of a development environment. Localizations for selected languages/locales integrate with application builds in the development environment so that updates are synchronized with project resources for multiple languages. This involves creating and employing localization files corresponding to source content of a project using a designated file format suitable to enable translations. Localization files that are created in the designated format may be exposed in various ways for translation via the system, a developer, a translation service, or other selected translation sources. A single multilingual resource file for an application is then generated to contain resources in multiple languages based on translations made available through the translation sources.

Abstract: Resource tracker techniques are described in which resource trackers may be generated, assigned to resources, and used to track resources throughout a development environment. The resource trackers may be configured in a designated format that is suitable to distinguish different resources one from one another. In one approach, resource trackers are derived as a combination of a user-supplied project identifier and defined resource identifiers. Resource trackers may be embedded into code defining corresponding resources and exposed to identify resources in connection with various development operations. In an embodiment, the resources trackers may be employed to provide visual indications of resources that appear within a user-interface for a project that is output for testing. A developer may identify resources based on resource trackers exposed via the user-interface and navigate back to underlying code in various ways to address any issues identified through the testing.

Abstract: Integrated application localization techniques are described in which support for application localization is provided as an integrated component of a development environment. Localizations for selected languages/locales integrate with application builds in the development environment so that updates are synchronized with project resources for multiple languages. This involves creating and employing localization files corresponding to source content of a project using a designated file format suitable to enable translations. Localization files that are created in the designated format may be exposed in various ways for translation via the system, a developer, a translation service, or other selected translation sources. A single multilingual resource file for an application is then generated to contain resources in multiple languages based on translations made available through the translation sources.

Abstract: Multilingual build integration for compiled applications is described in which support for application localization of compiled programming languages is provided as an integrated component of a development environment. Localizations integrate with application builds in the development environment so that updates are synchronized with project resources for multiple languages. This involves producing translation target files (e.g., localization files) for one or more selected languages by parsing and interpreting source files for the project to identify resources for translation. Localization files in the project that have been updated may be exposed in various ways for translation via the system, a translation service, or other translation source. Translated localization files are used to create dynamic resource files for the particular programming language that are compiled as part of the build process into language specific resource files.

Abstract: Creation and management of electronic files for a localization project. The electronic files are based on a data structure that defines the format and content of the electronic files and includes a first data structure portion that contains data that represents a plurality of references to localization project files. Moreover, the data structure includes a second data structure portion that is associated with the first data structure portion that contains data that represents a plurality of references to standard files.

Abstract: A localization development system includes a platform that receives information to be localized to a target market that is distinct from a source market for which the information was originally authored. The platform calculates a recycle rate for the received information. The recycle rate is indicative of a portion of the information that has already been localized to the target market before the information to be localized was received from an authoring component.

Abstract: Methods, apparatus, and computer-readable media employing computer-readable components for localization of data included in software programs are described. The computer-readable components comprise data elements defined based on a software data schema; and an owned comment data element comprising information about the localization of the data included in the software programs and an associated owner with permission to create, access, and manipulate the owned comment data element. The owned comment data element is included in other data elements. The owned comment data element may also be included in a list of owned comment elements comprising at least one owned comment data element.

Abstract: A localization platform is used to localize data to one or more distinct markets. A matching component receives data to be localized and accesses different localization components and returns localized data corresponding to the input data. A data gathering component receives localized content from an input source that is external to the localization platform along with metadata that identifies the particular input source that provided the localized content. The data gathering component then only allows the particular input source that provided the localized content to modify that localized content.

Abstract: Methods, apparatus, and computer-readable media including computer-readable components for the localization of data included in software programs are described. The computer-readable components comprise data elements defined by a software data schema; a property repository data element for storing a plurality of data properties about the data elements; and an owned comment data element comprising information about the localization of the data included in software programs and an owner with permission to create, access, and manipulate the owned comment data element.

Abstract: A user interface and associated methods for machine aided authoring and translation is provided. The user interface can display strings and associated metadata to assist with authoring and translations. The metadata can be used to mark the strings. The metadata can include one or more constraints which correspond to evaluation criteria and one or more anchor points operable to project the constraints against a string.

Abstract: Embodiments of a localization system are disclosed. In one embodiment, a plurality of localization components provide localized data that is localized to one or more distinct markets. A translation matching component receives a localization request corresponding to input data to be localized. The translation matching component accesses the plurality of localization components based on the localization request. The translation matching component selects and outputs localized data from one or more of the plurality of localization components based on pre-determined criteria. In one embodiment, the translation matching component selects the localized data based on a time required to obtain the localized data. In another embodiment, the localization components provide confidence scores associated with the localized data, the translation matching component selecting the localized data based on the confidence scores.