Code Conversion Using Segmented Mapping Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing code conversion methods face challenges when converting from a larger source encoding space to a smaller target encoding space, leading to truncation issues and loss of language features, particularly when dealing with character sets like Unicode and EBCDIC, where the target encoding space is exhausted, resulting in unreadable and featureless representations of rare words.
Innovation Solution
A method and system that generate a main conversion file and an extension converted file using a pre-established mapping table, which groups rare words by language features to share a single code point in the target encoding space, extending the target encoding space by combining these files, thus preserving language features and enabling correct representation of rare words.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If code conversion is performed from a larger source encoding space to a smaller target encoding space using traditional methods, then the conversion process is simple, but the target encoding space is exhausted and rare words cannot be represented
Solution Approach 1:
The patent divides the conversion system into two separate files: a main conversion file containing standard code point mappings, and an extension conversion file containing rare word mappings. This segmentation allows the system to handle both common and rare characters without exhausting the target encoding space, as rare words are stored separately with their language features preserved.
Solution Approach 2:
The patent extends the traditional single-dimension code point mapping by adding a second dimension through the extension conversion file. Rare words are mapped not only to code points but also associated with language features (radical, stroke count, pronunciation), creating a multi-dimensional representation that overcomes the limitations of the smaller target encoding space.
2Reliability
If code conversion truncates the source file to fit the target encoding space, then the conversion completes successfully, but language features are lost and rare words become unreadable
Solution Approach 1:
The patent performs preliminary classification of characters during the conversion process, identifying rare words and separating them into the extension conversion file before final conversion. This preliminary action ensures that rare words are not truncated or lost, and their language features are preserved in advance for later retrieval and display.
Solution Approach 2:
The extension conversion file acts as an intermediary between the source encoding space and the target encoding space for rare words. It stores the mapping information and language features separately, allowing the system to retrieve and reconstruct rare word representations without losing information, thus mediating between the constraints of the target encoding space and the requirements for complete information preservation.
3Productivity
If a pre-established mapping table is used for code conversion, then the conversion process is efficient, but rare words cannot be mapped when the target encoding space is exhausted
Solution Approach 1:
The extension conversion file serves multiple functions: it stores rare word mappings, preserves language features (radical, stroke count, pronunciation), and provides a lookup mechanism for reconstructing rare word representations. This multi-functionality allows the system to maintain high conversion efficiency while simultaneously handling rare words that would otherwise be unmappable in the smaller target encoding space.
Data Source
AI summary
Embodiments relate to a system, method and program product for performing code conversions. In one embodiment the method includes determining size of encoding space for a source file and a target file upon receipt of a code conversion request and generating a main conversion file upon determination that a target encoding space associated with said target file is smaller than a source encoding space associated with the source file. Subsequently an extension converted file is generated from the source file according to a pre-established mapping table of code conversion stored in a memory. The code conversion request is completed by using the main conversion file and said extension file together so that the source file does not need to be truncated in order to fit into the target conversion space.