Abstract: Translation capability for language processing determines an existence of an abbreviation, followed by non-exact matching to map the abbreviation to the original full term. A received string in a source language is provided as input to a translation service. Translation proposals in a different target language are received back. A ruleset (considering factors, e.g., camel case format, the presence of a concluding period, and/or consecutive consonants) is applied to generate abbreviation candidates from the translation proposals. Non-exact matching (referencing e.g., a comparison metric) may then be used to map the abbreviation candidates to text strings of their original full terms. A mapping of the abbreviation to the text string of the original full term is stored in a translation database comprising linguistic data. Embodiments leverage existing resources (e.g.

Abstract: Translation capability for language processing determines an existence of an abbreviation, followed by non-exact matching to map the abbreviation to the original full term. A received string in a source language is provided as input to a translation service. Translation proposals in a different target language are received back. A ruleset (considering factors, e.g., camel case format, the presence of a concluding period, and/or consecutive consonants) is applied to generate abbreviation candidates from the translation proposals. Non-exact matching (referencing e.g., a comparison metric) may then be used to map the abbreviation candidates to text strings of their original full terms. A mapping of the abbreviation to the text string of the original full term is stored in a translation database comprising linguistic data. Embodiments leverage existing resources (e.g.

Abstract: An engine interposed between an application translator and UI intercepts string templates populated with string variables and output by the translator. The engine determines translation-resistance of the string template. Such determination can be based upon an existing mark inserted by the translator, a number of string variables in the string template, a comment in the string template, user settings, or syntax rules. Frequently, translation-resistance of the string template is not indicated and the engine simply forwards on the string template to the user. Less frequently, the engine determines the string template to be resistant to translation. Then, the engine causes the string template to be processed according to a prefix and a suffix inserted thereto. The processing can comprise forwarding the string template for machine translation, and/or falling back to a simpler string variant. The modified content resulting from the processing is communicated by the engine to the user.

Abstract: Techniques and solutions are described for translating strings in a human language that are associated with code, such as code that declares user interface elements in association with which the strings can be displayed. The strings can be embedded in code, or can be included in files that are accessed by the code or used in creating executable code. Strings can be extracted from data, such as files, received in a translation request. After translation, such as by a human translator or using automatic translation, the translation results can be provided in response to the translation request. The translation process can be automated, such that changes to files in a code repository can trigger a translation request. Disclosed technologies can facilitate the production of programs that are localized using different human languages.

Abstract: An engine interposed between an application translator and UI intercepts string templates populated with string variables and output by the translator. The engine determines translation-resistance of the string template. Such determination can be based upon an existing mark inserted by the translator, a number of string variables in the string template, a comment in the string template, user settings, or syntax rules. Frequently, translation-resistance of the string template is not indicated and the engine simply forwards on the string template to the user. Less frequently, the engine determines the string template to be resistant to translation. Then, the engine causes the string template to be processed according to a prefix and a suffix inserted thereto. The processing can comprise forwarding the string template for machine translation, and/or falling back to a simpler string variant. The modified content resulting from the processing is communicated by the engine to the user.

Abstract: Techniques and solutions are described for translating strings in a human language that are associated with code, such as code that declares user interface elements in association with which the strings can be displayed. The strings can be embedded in code, or can be included in files that are accessed by the code or used in creating executable code. Strings can be extracted from data, such as files, received in a translation request. After translation, such as by a human translator or using automatic translation, the translation results can be provided in response to the translation request. The translation process can be automated, such that changes to files in a code repository can trigger a translation request. Disclosed technologies can facilitate the production of programs that are localized using different human languages.

Abstract: A request to translate an input collection of collocated separate strings from a source language to a target language is received. The input collection is associated with a combination of meanings for the collocated separate strings within a context of the input collection. A search for the collocated separate strings is performed in a database storing a number of collection units of separate strings in the source language and a correspondingly translated number of collection units of translated separate strings in the target language. An output collection unit of separate strings in the target language is determined as a translated collection of separate strings of the input collection based on evaluating the input collection as a unit and evaluating the number of collection units of separate strings in the source language and the correspondingly translated number of collection units of translated separate strings in the target language at the database.

Abstract: A request to translate an input collection of collocated separate strings from a source language to a target language is received. The input collection is associated with a combination of meanings for the collocated separate strings within a context of the input collection. A search for the collocated separate strings is performed in a database storing a number of collection units of separate strings in the source language and a correspondingly translated number of collection units of translated separate strings in the target language. An output collection unit of separate strings in the target language is determined as a translated collection of separate strings of the input collection based on evaluating the input collection as a unit and evaluating the number of collection units of separate strings in the source language and the correspondingly translated number of collection units of translated separate strings in the target language at the database.