Control-D/WebAccess Server Font Mapping

Font mapping maps original print stream fonts, such as, AFP, Xerox, and PostScript to other types of fonts, such as, TrueType fonts or web-enabled fonts, which enables you to transform reports in the Control-D/WebAccess Server Web Application. You can define fonts in the Font Mapping Editor. Font mapping uses a pre-supplied fontmap.tbl default font mapping table, which includes a list of AFP and Xerox fonts and recommended mappings. The Font Mapping Editor guarantees that documents look the same across various systems and devices when you transform a report.

Font mapping enables you to do the following:

• Ensure document consistency by aligning fonts across diverse systems and devices.

• Enhances compatibility by substituting fonts, which accommodates variations in font availability.

• Supports localization efforts, which enables proper rendering for different languages and character sets.

• Optimizes printing processes by choosing printer-friendly fonts, which reduces printing issues.

Mapping Fonts

This procedure describes how to map or modify fonts in the Font Mapping Editor tool, which enables you to transform AFP and XEROX reports.

Begin

1. From the Tools drop-down list, select Font Mapping Editor.

   The default font mapping file, fontmap.tbl, appears in the Font Mapping Editor window.

2. (Optional) Do the following to open a different font mapping file:

   1. From the toolbar, click File, and then select Open.

      The Open Font Table window appears.

   2. Select a file and click OK.

      The selected font mapping file appears in the Font Mapping Editor window.

3. In the Original Font field, select the line to map the font.

4. For each field, define the required parameters, as described in Font Mapping Editor Parameters.

5. (Optional) Click File, then click Save As, which enables you to save the changes in a different file.

6. Click Save.

   A font is mapped.

Font Mapping Editor Parameters

The following table describes the Font Mapping Editor parameters, which enables you to map AFP and XEROX fonts.

Parameter	Description
Original font	Determines the original AFP, Xerox, PostScript, or PCL font name, or mask. You can use the following wildcard characters: to define masks: ?: Represents any one letter. *: Represents any number of letters. PCL font names appear in the pclglue.glu file. PostScript font names appear in the PostScript report. You must define the font name when a font name contains the suffix -ISL.
Original Weight	Adjusts the lightness or boldness of the font: Valid values: 200 (Extra Light) - 900 (Heavy).
Original Style	Determines whether the font is upright (Roman) or italic.
True Type (.ttf)	Defines the name of the corresponding (mapped) TrueType font.
PostScript Font File name	Defines the filename which contains the font to transform PostScript reports. You can define a file that contains a font other than the original font, which maps this font to the original font. For the PostScript font AvantGarde-Book, you can define either of the following font files: TT0156M_.ttf: This file contains the original AvantGarde-Book font. Arial.ttf: AvantGarde-Book font maps to Arial.
PostScript Raster	Enables you to raster fonts on the bitmap by the PostScript Interpreter when you transform report. Valid values:  Yes No Default: No
HTML	Determines the name of the corresponding (mapped) HTML font so that web browsers can use them. Valid values: Empty: Text renders directly on the PNG image when you use a TrueType font, as there is no separate HTML section involved. None: Excludes the font in the HTML output. BMC recommends that you enable this checkbox when you use a shading font, which is too dark in HTML. Raster: Rasters the original font on the PNG background.
HTML Family Type	Determines the HTML font family type. The browser selects an alternative font from the font family specified in the HTML Family field when you do not determine a font in the HTML field. Valid values: Cursive: Typeface style that emulates handwritten letter forms which inclines to the right. Fantasy: Generic category that includes decorative or display fonts Desdemona Nonospace: A non-proportional font where each character uses the same width. The letter I takes up the same space as the letter M. Other: Font that does not belong to the other categories. Sans Serif: Typeface style without serifs. Arial Serif: Typeface style which contains short horizontal lines added at the top and bottom of the vertical parts of a letter. Times New Roman
HTML Weight	Determines the lightness or boldness of the HTML font. Valid values:200 (Extra Light) - 900 (Heavy).
Spacing	Determines the narrowing or widening of spacing between letters. Valid values: −10−10 Default: 0
HTML Style	Determines the HTML font is upright (Roman) or Italic.
EOT	Defines EOT web-enabled font name, as described in Map to web-enabled Fonts.
PFR	Define the PFR web-enabled font name, as described in Map to web-enabled Fonts.

Converting and Mapping Fonts

This procedure describes how to convert and map a group of fonts, AFP fonts, and XEROX fonts to a TrueType font, which enables you to use TrueType fonts and optimize reports.

Begin

1. From the Tools drop-down list, select Font Mapping Editor.

   The Font Mapping Editor window appears.

2. From the Font Mapping Editor window, click the Add New Fonts.

   The Add New Fonts dialog box appears and lists original fonts in the default resource directory.

3. From the Fonts List, select the required fonts that you want to map in the New Fonts Added.

4. Click Add or Add All.

   The current mapping overrides the earlier mapping when you select a mapped font.

5. From the Mapping area, do one of the following actions:

   • From the Map to drop down list, click the required TrueType font.

   • Select the Convert & Map checkbox to convert an original AFP or Xerox font.

6. To compare the original font to the selected output font, do the following:

   1. Click Compare.

   2. Select the AFP or Xerox checkbox and click OK.

   3. The Font Compare window appears.

   4. Compare the fonts, as described in Comparing Fonts.

7. Click Map to accept the defined mapping.

8. Repeat the steps as required.

9. Click Map & Close.

   The converted and mapped font appears in the Font Mapping Editor window.

Comparing Fonts

This procedure describes how to compare font, which enables you to compare the selected output font against the original font, before you transform reports.

Begin

1. Open the Font Compare window, as described in Step 1-6 in Converting and Mapping Fonts.

2. Define a test string in the String Testing field.

3. In the Original Font selection field, select the original font.

4. In the New Font selection field, select the desired TrueType font.

5. Click Apply.

   The character set and the test string appear for both fonts.

6. Click Map to approve the mapping combination.

7. Otherwise, select other TrueType fonts to compare.

8. Repeat the steps as required.

9. Click Close.

10. Click Map & Close.

    The converted and mapped font appears in the Font Mapping Editor window.

PostScript Fonts Mapping

PostScript reports reference External fonts for those not included in the PostScript report, or Embedded fonts that are part of the PostScript report itself. You do not need to map standard fonts, such as Courier, Time New Roman, or Helvetica. You must include the PostScript font filename in the fontmap.tbl file when you use non-standard PostScript External fonts, which uses a standard encoding when Times New Roman is the default font, and the field is blank.

PostScript Embedded fonts appear as an image unless you map them, as described in Converting and Mapping Fonts.

Map to web-enabled Fonts

Web-enabled fonts enable you to view HTML pages by using HTML fonts that reside on the server. The server fetches dynamic or embedded fonts on demand. Microsoft Corporation and Bitstream Inc. offer mechanisms to support web-enabled fonts. BMC does not supply the following products, which are available for purchase independently:

• Microsoft: Embedded OpenType (EOT) fonts.

• Bitstream: Portable font resource (PFR) fonts.

Viewing Print Stream Reports on the Control-D/WebAccess Server Web Application

This procedure describes how you can use web-enabled fonts in Control-D/WebAccess Server Web Application to ensure consistent, readable, and accessible print stream reports across various digital platforms and web browsers.

Before you Begin

• Generate TrueType fonts from the original AFP or Xerox fonts used by the relevant reports, as described in Converting and Mapping Fonts.

• Use the generated TrueType fonts to create EOT or PFR web-enabled HTML fonts, as described in Configuring Microsoft or Bitstream Products.

Begin

1. Map original AFP or Xerox fonts to web-enabled fonts, as described in Converting and Mapping Fonts.

2. Prepare the Microsoft of Bitstream products, as described in Configuring Microsoft or Bitstream Products

3. Update the driver, as described in Updating the Microsoft or Bitstream Driver:

   1. Define the Driver information on the Font Mapping Editor.

   2. Map the original fonts to the EOT or PFR fonts.

Configuring Microsoft or Bitstream Products

The following procedure prepares the Microsoft or Bitstream products you can use to map fonts and are not functions of Control-D/WebAccess Server.

Begin

1. Generate the Microsoft EOTs or BitStream PFRs for the fonts your reports require.

   You must include the following:

   • The URLs where pages are located.

   • The URL of your Control-D/WebAccess Server Web Application.

     Use either the URL, such as http://www.yoursite, or use the explicit IP address, such as http://172.96.7.21.

     You must identify the IP address for each Control-D/WebAccess Server Web Application that uses these fonts.

2. Declare the PFR MIME type at your server.

   • MIME type: application/font-tdpfr.

   • File extension: pfr.

3. Customize tdserver.js.

   Edit the tdserver.js file and set the URL for the server to the location of the tdserver.cab related to the wfplayer.

Updating the Microsoft or Bitstream Driver

This procedure describes how to update the Microsoft or Bitstream Driver after you configure Microsoft or Bitstream Products, as described in Configuring Microsoft or Bitstream Products.

Begin

1. From the Tools drop-down list, select Font Mapping Editor.

2. From the Font Mapping Editor window, click Tools, and then select Drivers.

3. Fill in the fields as follows:

   • Bitstream: Define the appropriate URL in the PFR field.

   • MIcrosoft EOT: Define the appropriate URL in the EOT field.

4. Click OK.

   The driver is updated.

Effect of font mapping on output types

The following table lists the different types of output and describes the effect of font mapping on each output type.

Output type	Effect
Bitmap	The font does not raster as an image on the bitmap, and appears a TrueType font when you map a font to TrueType.
PDF	The font always embeds in the PDF file as text, even though the correct TrueType font is installed when you map a font to TrueType.
HTML	One of the following actions occurs: The output uses defined EOT or PFR fonts first. The browser selects the closest font which is similar to the HTML font family when you select a different font in the HTML field. The font does not appear in the HTML when you select none. The Transformation process rasters the original font when you select raster even though a TrueType font exists. The font appears on a background PNG image when you do not define the HTML field.
PCL	The font does not raster as an image on the bitmap, but appears a TrueType font when you map a font to TrueType.