![practicing subscript and superscript in word practicing subscript and superscript in word](http://www.runeman.org/tips/word/subsuper/Image13.gif)
For instance, you would have a static font asset for Latin languages which could include Cyrillic. Static font assets should contain all the known characters used in a project for any given language or groups of language. Most users use a combination of static and dynamic font assets. static or not if the source font file is like 60mb like some of the CJK font files.
![practicing subscript and superscript in word practicing subscript and superscript in word](https://images.tips.net/S06/Figs/T8841F1.png)
Again, depending on the size of the source font file, that could be a saving on build size vs. Dynamic font assets also require that we include their source font file in the build. Dynamic font asset have a higher performance overhead since we need to be adding these characters and glyphs to the atlas texture at runtime. Their contribution to build size in some cases can be lesser than dynamic font assets but that all depends on the size of the source font file.ĭynamic font assets should be used for unknown characters which typically come from user input. Their memory overhead is no greater than dynamic font assets. In a build and at runtime, their source font file is no longer needed thus potentially saving on build size. Static font assets provide better performance since everything is already baked in. Since Chinese, Japanese and Korean languages contain a lot of characters, you would most likely have a separate static font asset for each. Click to expand.Static font assets should contain all the known characters used in a project for any given language or groups of language.