
Note that by default each installation includes a font module (fonts.jar) containing font metrics for a few standard fonts. However, they may not be the same fonts as those used in Hx/Px graphics
installed on an embedded controller.
Also, note that Hx/Px graphics using multiple fonts may require that you use this tool to create a separate font metric file for each font. Multiple font files can then be bundled in a new module for ease of installation on embedded controllers.
Naturally, a best practice would be to limit font usage in Hx/Px graphics to a select few fonts that you create font files for or to limit usage only to the fonts contained in the default font module.
Use this tool when all of the following are true:
Java Virtual Machine type listed in the Platform Administration view, (as shown), and:
By default the installation includes a fonts module that contains .font files with font metrics for the first 256 code points for the font families, point sizes, and styles listed in the following table.
| Font families | Arial, Courier New, Source Sans Pro (Zebra Theme default font), Tahoma (Lucid Theme default font) |
| Font point sizes | 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72 |
| Font styles | Plain, Bold, Italic, Bold + Italic |
For a given font family listed in the table (such as Arial) there is a separate font file for each combination of point size plus font style. For example, a separate font file is available in the default font module for each of the following combinations:
Arial 8pt Arial 8pt Bold Arial 8pt Italic Arial 8pt Bold Italic Arial 9pt Arial 9pt Bold Arial 9pt Italic Arial 9pt Bold Italic ... etc.
Follow the on-screen instructions in the tool to generate the .font files you need. For best results, generate metrics using this tool on the same operating system you'll be using to view Hx/Px pages in a web browser.
You can install the .font files you have generated to this location on the embedded device:
My File System/User Home/shared/microFont
Finally, restart your station so that your new .font files are properly loaded.
You can package your .font files into a separate module or include them in your theme's module.
microFont that is located at the root of your module. <def> block to your new module's module-include.xml file: <defs> <def name="microFont" value="YourNewModuleNameHere" /> </defs> module-include.xml file:<installation noRunningStation="true"/>This invokes a station reboot upon module installation, ensuring that your new .font files are properly loaded.The framework will search for .font files in three locations in the following order:
My File System/User Home/shared/microFont. microFont folder with .font files inside and a <def/> in their module-include.xml. module://fonts/microFont).