The most optimized and efficient way to do this is to select a sub-set of glyphs that can be used in some language, and only export this set of glyphs for that specific language. SWF extension)Īfter you set up all the fonts you wish to use in the UI, you should create localized copies of the font library for each language you wish to support. The sharing URL should be set to the name of the final GFX file (with. This is the name will be used in flash files using this font. Make sure to check both the export checkboxes, and set the Identifier to an unique name. Go to the font's properties to set up the export settings. However, you can create your own if you prefer to create a font library from scratch.įor each distinct font you wish to use, create new font symbols and set the font-style in the library ( Right-Click -> New font). The flash file used to generate this GFX in the SDK can be downloaded from here as a sample: HUD_Font_LocFont.fla. In the GameSDK sample project, we use the library HUD_Font_LocFont.gfx file. It is possible to set up a font library with more than one font (with different Action Script export names), but in the GameSDK sample we only use one. When dynamic text is composed by the user, the glyphs will be loaded by Scaleform from this source file. Setup font libraryĪ font library is a GFX file that exports Action Script symbols describing a font, and contains the associated glyph data to render the font in the game. It also makes sure that your design is consistent over all UI assets and changes are even easier since it is only necessary to change one file per language to switch the font for the whole UI. This technique also allows embedding different glyph sets for different languages. One reason is to save memory since you don't want to embed every font in every flash file. It is recommended to use one font library for all flash assets. PUIElement->SetVariable("MyTextbox", libraries and glyph sets IUIElement* pElement = pFlashUI->GetUIElement("MyElement")
0 kommentar(er)
