Translation Engine for Web App String Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing UI translation technologies face challenges in handling translation-resistant string templates due to differences in languages, such as gender, case, and plural forms, leading to inaccurate or untranslatable outputs.
Innovation Solution
An engine is interposed between the application translator and the UI to determine translation-resistance by considering marks, number of variables, comments, user settings, and syntax rules, and applies machine translation or falls back to simpler variants by adding invisible prefixes and suffixes to such templates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If text templating with translated text variables is used in UI design, then the UI can support multiple languages, but translation-resistant content (domain-specific strings) cannot be accurately translated into languages with different grammatical structures
Solution Approach 1:
The patent introduces an intermediary component (translation engine or processing layer) between the UI template system and the translation output. This intermediary detects translation-resistant content and applies specialized processing rules, allowing the system to maintain multi-language support while handling domain-specific terminology that resists standard translation methods
Solution Approach 2:
The system changes the translation parameter state by identifying content marked as translation-resistant and applying different processing parameters to such content. This allows the same translation system to handle both easily translatable content and resistant content with appropriate parameters, maintaining accuracy for domain-specific strings while supporting multiple languages
2Reliability
If the engine processes all string templates through machine translation, then translation coverage is improved, but processing time and computational resources increase
Solution Approach 1:
Instead of applying machine translation to all string templates uniformly, the system applies partial action by selectively processing only those templates identified as translation-resistant. This reduces unnecessary processing time for already-translatable content while maintaining comprehensive translation coverage for resistant content
Solution Approach 2:
The system performs preliminary action by pre-identifying and marking translation-resistant content before the actual translation process. This allows the translation engine to prepare appropriate processing strategies in advance, reducing runtime processing time while ensuring complete translation coverage
3Manufacturing precision
If the engine applies complex translation processing to all strings, then translation quality improves, but system complexity increases
Solution Approach 1:
The system applies local quality by providing different processing qualities to different parts of the content. Translation-resistant strings receive complex, high-quality processing with specialized rules, while standard strings receive simpler processing. This maintains high translation quality for difficult content without unnecessarily complicating the entire system
Data Source
AI summary
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.