Official translation unavailable. Translate this page with Google:

You might design your label templates to print text objects using internal printer fonts. These are the fonts that are stored in your printer's memory. If you try to print such labels on a different kind of printer, the selected internal fonts might not be available. The new printer probably supports an entirely different set of internal fonts. The font layout might be similar in such case, but is available under a different name.

Font mismatch might also occur if the Truetype font that you are using on your labels is not installed on the computer on which you run Designer to design and print labels.

You can configure Designer to automatically replace the fonts used on the label with compatible fonts. In such a case, Designer maps and replaces the fonts using their names. If the original font is not available, Designer uses the first available replacement font defined in the mapping table.

If there are no suitable replacement fonts, Designer uses the Arial Truetype font.

Note

After configuring the font replacement, mapping rules execute when you change the printer for your label.

Configuring Font Mapping

  1. Open file explorer and navigate to the following folder:

    %PROGRAMDATA%\NiceLabel\NiceLabel 10
  2. Copy fontmapping.def file to fontmapping.local.def.

  3. Open the fontmapping.local.def file in your favorite text XML editor.

  4. Inside the element FontMappings, create a new element with a custom name.

  5. Inside the new element, create at least two elements named as Mapping.

    • Value of the first element named Mapping must contain the name of the original font.

    • Value of the second element named Mapping must contain the name of the replacement font.

      Note

      Additional Mapping elements with new font names are allowed. If the first replacement font is not available, Designer tries the next one. If no replacement fonts are available, Arial Truetype is used instead.

      Note

      The file fontmapping.local.def is your file and is preserved during the upgrades. On the other hand, fontmapping.def belongs to NiceLabel and is overwritten during the upgrades. Do not modify the fontmapping.def file.

Sample Mapping Configuration

In the below shown example, two mapping rules are defined.

  • The first mapping rule converts any Avery font into a matching Novexx font. For example, a font named Avery YT100 will be replaced with a font named Novexx YT100, and a font named Avery 1 will be replaced with a font named Novexx. If the Novexx font is not available, Arial Truetype font will be used.

  • The second mapping rule converts a font named Avery YT100 into a font named Novexx YT104. If this font is not available, font Zebra 0 will be used. If this font is also not available Arial Truetype will be used.

  • The second mapping rule overrides the first one.

<?xml version="1.0" encoding="utf-8"?>
<FontMappings>
    <Avery_DennisonNovexx>
        <Mapping>Avery Dennison</Mapping>
        <Mapping>Novexx</Mapping>
    </Avery_DennisonNovexx>
    <TextReplacement>
        <Mapping>Avery YT100</Mapping>
        <Mapping>Novexx YT104</Mapping>
        <Mapping>Zebra 0</Mapping>
    </TextReplacement>
</FontMappings>