You shouldn’t pay a penalty for beautiful, international text. A font engine that takes up too much memory space, slowing a device down and getting in the way of the interesting stuff, won’t go down well with customers. Which is why we’ve optimized our software to keep the lowest profile, with a compact file size and a simple integration process that will leave even the most memory-constrained environment undisturbed. What’s more, we offer engineers additional memory controls via compression and font linking. Learn more below.
In resource constrained environments, the first place to turn to for text is often bitmap type. With the help of Spark, you no longer need to sacrifice text quality as our solution lets you execute dynamic, fully scalable fonts within your devices. Scroll the slider above to see the quality impact or a dynamic font versus a bitmap solution.
If your device needs to carry multiple languages and font styles, we can help lighten the load. Monotype has a number of tried and tested compression technologies that can dramatically reduce the size of font files, including those of Asian fonts that take big bites out of disk space. For some Asian fonts with large character counts, the overall font load can be cut by several megabytes through compression.
Font linking gives you just one font file to manage. Unlike the Freetype offering, instead of loading multiple font files or lumping all your languages in one heavy file, we link several files and serve them dynamically from the cloud. Font linking points your application to a reader file prioritized according to the languages most in-use in the region where your product is shipping.
A car being shipped to Japan, for example, would first search and serve Japanese character sets, followed by Latin or Korean. If it was headed to Canada, it would first serve Latin characters followed by Arabic. With just one font file to manage, you can serve multiple languages with just a quarter of the memory space you’d need to load them individually.