In our daily work, we often need to open documents on different devices and operating systems. To ensure that documents appear as the author intended, fonts play a crucial role. However, font rendering in online document preview scenarios presents several challenges. Today, let’s delve into the efforts EO2Suite has made in its font fallback mechanism and how we’ve optimized it to make online document previews more seamless.
The Challenges of Online Font Rendering
Online document previews, unlike local applications, cannot directly access the user’s local font files. This leads to two key issues:
- **Limited Font Resources:** We cannot rely on the fonts installed on the user’s system, as local applications do. For display purposes, we need to download font files from a server.
- **Font Copyright Restrictions:** Commercial fonts typically require licensing, and we cannot directly host these paid fonts on a server for users to download. Therefore, we must choose to use free fonts.
These two challenges make font fallback crucial in online documents. If a user’s chosen font is not on our font list, we need to find a suitable substitute. A poor fallback logic can lead to distorted text, severely impacting the user experience.
EO2Suite’s Font Fallback Mechanism: A Detailed “Font-Finding” Journey
EO2Suite has put a lot of effort into this area. Instead of simply selecting a default font, they’ve built a complex fallback mechanism based on “penalty value calculation” and “Unicode index.”
1. Font Dictionary: A Comprehensive “Font Map”
First, EO2Suite maintains a vast font dictionary containing:
- **Font Names:** e.g., Arial, Times New Roman.
- **Unicode Ranges:** Describing the supported Unicode character range for the font.
- **Font File Sizes:** Used to evaluate download costs.
This font dictionary serves as a detailed “font map,” helping EO2Suite quickly locate available font resources.
2. Penalty Value Calculation: Selecting the Best Substitute
When a user’s chosen font is not in the dictionary, EO2Suite calculates a “penalty value” for each candidate font using the information in the dictionary. This penalty value considers:
- **Similarity of Font Names:** For example, if a user selects “Arial Bold”, a font named “Arial” in the dictionary would have a relatively lower penalty value.
- **Matching Unicode Ranges:** If a document contains many Chinese characters, fonts supporting Chinese would have lower penalty values.
- **Font File Size:** Smaller fonts download faster, so they have lower penalty values.
Ultimately, EO2Suite chooses the font with the smallest penalty value as the fallback font and downloads it. This tries to ensure the displayed document is as close to the user’s expectation as possible.
3. Unicode Index: A Last “Resort”
However, even after selecting a fallback font with penalty value calculations, the target font might still lack specific characters in the user’s document. At this point, EO2Suite uses a final fallback mechanism: the Unicode index.
EO2Suite generates a Unicode index in advance, dividing the entire Unicode space into segments, and each segment corresponds to a font that covers it. This font is the smallest file size font from the supported list. This ensures that any character can find a corresponding glyph in the font set, minimizing instances of characters displayed as “squares.”
Our Optimization: Special Care for Chinese
EO2Suite’s font fallback mechanism is already quite robust, but there was still room for improvement in Chinese character display. Considering the complexity and diversity of Chinese fonts, we enhanced the mechanism:
- **Introducing Open-Source Chinese Fonts:** We added high-quality open-source Chinese fonts such as Source Han Sans and Source Han Serif. These fonts cover a wider range of Unicode and display Chinese characters better.
- **Hardcoding Fallbacks for Common Fonts:** We hardcoded fallbacks for common Chinese fonts like Microsoft YaHei, Songti, Heiti, and PingFang to Source Han Sans or Source Han Serif. This ensures that when users select these common fonts, they fall back to the most appropriate Chinese fonts.
These optimizations have significantly improved the issue of garbled Chinese characters, making the display of Chinese documents more accurate and aesthetically pleasing.
Conclusion
Font fallback is a complex but crucial technical aspect that directly affects the user experience. EO2Suite, through its detailed font dictionary, penalty value calculations, and Unicode index, has built a robust fallback mechanism. And based on that, we have optimized it for Chinese, further enhancing the online document preview experience.
Of course, font display is a continuous process of optimization. With the advancement of technology, we will continue to explore better solutions to make online document fonts appear perfect.
I hope this article helps you better understand EO2Suite’s font fallback mechanism. If you have any questions or suggestions, please feel free to leave them in the comment section below.
发表回复