Interface Display Resource Separation for Faster Language Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing applications (APPs) face challenges in efficiently supporting multiple languages without requiring extensive integration of language resources into their interfaces, leading to slower loading times and reduced flexibility in language switching.
Innovation Solution
A method for displaying interfaces that separates language resources from interface data, allowing for rapid acquisition and display of multi-language support by using a unified standard express APP that leverages a server to provide language resources independently of the interface data, enabling quick switching between language environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If language resources are integrated into interface data, then multi-language support is achieved, but interface loading time increases and flexibility decreases
Solution Approach 1:
The patent segments language resources from interface data by using separate resource files (e.g., strings.xml for UI text, colors.xml for color definitions, dimensions.xml for dimensional definitions). This allows the interface structure to be loaded independently while language-specific resources are loaded separately, reducing initial loading time and enabling selective loading of language resources based on user preferences.
Solution Approach 2:
Language resources are extracted from the main interface data package into separate, independently loadable resource files. The interface data contains only structural definitions and references to language resource identifiers, while actual language content is stored in separate files that can be loaded on-demand or cached separately, thus eliminating the need to load all language resources simultaneously with the interface.
2Adaptability or versatility
If language resources are integrated into interface data, then multi-language support is achieved, but resource volume and complexity increase
Solution Approach 1:
The patent divides language resources into multiple specialized resource files (strings.xml, colors.xml, dimensions.xml, styles.xml) rather than embedding all language content within the main interface data. Each file contains specific types of language resources, reducing the complexity and volume of individual interface data files while maintaining comprehensive multi-language support capability.
Solution Approach 2:
Language resources are extracted from the main interface data structure into separate, dedicated resource files. The interface data only contains structural definitions and references to resource identifiers, while actual language content is stored in external files that can be managed, cached, and loaded independently, significantly reducing the volume of core interface data.
3Adaptability or versatility
If language resources are integrated into interface data, then language switching is possible, but switching speed decreases due to reintegration requirements
Solution Approach 1:
The patent segments language resources into separate, independently loadable files that can be switched without affecting the core interface structure. When language switching is required, only the relevant language resource file needs to be loaded or swapped, rather than reprocessing the entire integrated interface data package, enabling rapid language switching.
Solution Approach 2:
Language resource files are prepared and cached in advance during application initialization or previous usage sessions. When a user switches languages, the system can quickly retrieve pre-cached language resources or load only the specific language file needed, rather than processing and integrating all language resources from scratch, thus achieving fast language switching.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
Interface data of a to-be-displayed interface of a first target application (APP) are acquired (201, 401). A first request is sent to a server (102, 1000) (201, 402). At least one language resource returned by the server (102, 1000) is received (201, 405). For each interface element in the interface data, a target language resource corresponding to the each interface element in the interface data is determined in the at least one language resource (202, 406). The to-be-displayed interface of the first target APP is displayed based on the interface data and the target language resource (203, 407).