7.12. Add-on options

7.12.1. Apache FOP options

The "FOP" preferences sheet is available only when add-on "Apache FOP 1.x XSL-FO processor plug-in" has been installed.

Figure 9.4. The "FOP" preferences sheet
The "FOP" preferences sheet

By default, only the 14 built-in fonts: Times, Helvetica, Courier, Symbol and ZapfDingbats are used in the generated PDF. The above preferences sheet allows to specify which custom TrueType (.ttf) fonts are to be embedded in the generated PDF.

This facility is useful in the following two cases:

  • The 14 PDF standard fonts (Helvetica, Times, Courier, etc), which are used by default by FOP, have glyphs only for the Western languages. If, for example, you convert a DocBook document written in Russian to PDF, the generated PDF will mainly contain the '#' placeholder character. Fortunately, widely available TTF fonts such as Microsoft® Arial, Times New Roman and Courier New or the DejaVu fonts have glyphs for almost all the languages of the world.

  • Use fonts nicer than the 14 PDF standard fonts.

Procedure 9.1. How to use Times New Roman, Arial and Courier New instead of Times, Helvetica, Courier
  1. Click Use Windows® standard fonts.

    Note that the Use Windows® standard fonts button is grayed if the Arial font is not found in the standard fonts folder of your system.

  2. Click OK.

  3. Restart XMLmind XML Editor.

Procedure 9.2. How to choose specific fonts (for example, you want to replace Times fonts by Georgia fonts)
  1. Click Add.

    This displays the following dialog box:

    Figure 9.5. The "Choose a TTF font and specify its aliases" dialog box
    The "Choose a TTF font and specify its aliases" dialog box

    1. Choose the .ttf file containing font "Georgia".

      Tip

      On Windows, for permissions reasons, there is no way to pick a font file from the "C:\Windows\Fonts\" folder using the standard file chooser. Therefore the only way to register with Apache FOP a font found in "C:\Windows\Fonts\" is to drag its file from the Windows file manager and to drop it onto the list found in the "FOP" preferences sheet (see above figure).

      However, after you do this, do not forget to select each entry added by the drop action and then click Edit to possible change or complement what's have been automatically specified there.

    2. Specify the following alias: serif.

    3. Click OK.

  2. Click Add.

    1. Choose the .ttf file containing font "Georgia Bold".

    2. Specify the following alias: serif, Bold.

    3. Click OK.

  3. Click Add.

    1. Choose the .ttf file containing font "Georgia Italic".

    2. Specify the following alias: serif, Italic.

    3. Click OK.

  4. Click Add.

    1. Choose the .ttf file containing font "Georgia Bold Italic".

    2. Specify the following alias: serif, Bold, Italic.

    3. Click OK.

  5. Click OK.

    Doing this automatically creates a standard FOP configuration file in XXE_user_preferences_dir/fop/fop.conf. User preferences directory XXE_user_preferences_dir is documented in Section 7, “The "Preferences" dialog box”.

  6. It is recommended to repeat the above steps in order to specify fonts replacing Helvetica, that is, fonts having a sans-serif alias and fonts replacing Courier, that is fonts having a monospace alias.

  7. Restart XMLmind XML Editor.

7.12.2. RenderX XEP options

The "XEP" preferences sheet is available only when add-on "RenderX XEP XSL-FO processor plug-in" has been installed.

XEP preferences are identical to FOP preferences. There are two minor differences though:

  • Some fonts have licensing restrictions that forbid embedding them in a PDF file. RenderX XEP enforces these licensing restrictions, not Apache FOP. XMLmind XML Editor has currently no way to detect these licensing restrictions, therefore you may follow the above procedure and end up with glyphs still missing in the generated PDF.

  • The standard XEP configuration file is created in XXE_user_preferences_dir/xep/xep.conf.