Web Document Font Handling via Glyph Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional web browsers face increased document load times due to the need to download large font files, especially for East Asian languages, which can frustrate users seeking on-demand document viewing.
Innovation Solution
Implementing local font files, a common font subset, and a per document font subset to reduce the amount of font data transmitted, allowing web browsers to utilize existing fonts for display without requiring full font downloads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the web browser downloads complete font files to display documents, then the document can be displayed with proper fonts, but the document load time increases significantly
Solution Approach 1:
The patent extracts only the necessary font data (specific glyphs) from complete font files. The server identifies which fonts are needed for the document and transmits only those specific character glyphs, eliminating unnecessary font data. This resolves the contradiction by maintaining font display quality while dramatically reducing download time and data transmission.
Solution Approach 2:
The patent segments the font file into individual glyph components. Instead of transmitting entire font files containing all possible characters, the system divides the font into discrete glyph elements and transmits only the segments (glyphs) that are actually needed for the specific document being viewed. This segmentation enables selective font data transmission.
2Adaptability or versatility
If the server transmits complete font files for every document, then all fonts are available for display, but the amount of data transmitted increases
Solution Approach 1:
The system extracts only the specific glyphs required for the document from the complete font files. The server analyzes the document content, identifies which characters are present, and transmits only those corresponding glyph images, removing all unnecessary font data. This maintains font availability for display while minimizing data transmission volume.
Solution Approach 2:
The patent applies partial action by transmitting less than the complete font file - only the portion (specific glyphs) that is sufficient for displaying the document. This partial transmission approach provides exactly what is needed without the excess of complete font files, reducing data size while maintaining functionality.
3Reliability
If the web browser waits for font files to download before displaying documents, then proper font rendering is ensured, but user frustration increases due to delayed viewing
Solution Approach 1:
The system extracts and transmits only the essential glyph data needed for immediate document display. By sending minimal font data (specific glyphs) rather than complete font files, the browser can quickly receive and render the document with proper fonts, reducing wait time while maintaining rendering accuracy. This resolves the contradiction between reliable font rendering and ease of on-demand viewing.
Solution Approach 2:
The server performs preliminary analysis of the document to identify which fonts and glyphs are needed before transmission. This preliminary action enables the server to prepare and send only the necessary font data in advance, allowing the browser to display the document quickly with proper font rendering from the start, rather than waiting for complete font files.
Data Source
AI summary
A request is received for a rendered document corresponding to a document. The document is retrieved from a storage device. The document is transformed into the rendered document. One or more server font files associated with the rendered document are generated. The rendered document and the server font files are stored.