5.2.031

738 FOP hyphenation

It is now possible to hyphenate with FOP. This is done automatically for FO objects with hyphenate = true for languages that both Skribenta and FOP hyphenation support. If a customer wants to develop an existing hyphenation pattern, or create a completely new pattern, the updated pattern file must be compiled and merged into fop-hyph.jar and placed in the shared folder. In case a new pattern file is created, it must also be declared in the FOP configuration file.

Contact Excosoft for more information.

737 FOP user configuration

It is now possible to specify custom fonts for FOP publishing. The fonts can be specified in a regular recipe using the following namespace convention:

[base].[font].[font-variant].[table with font variant attributes]

where

[base] = Skribenta.Publish.PDF.Fonts

[font] = The name of the font to be addressed with font family in the stylesheet

[font-variant] = An arbitrary descriptive name that contains specifications for a font variant, e.g., normal, bold or italic.

The font variant attributes follow FOP syntax. The following FOP font variant attributes have been implemented in Skribenta:

* embed-url: Link to the font file to be embedded

* metrics-url: Link to the metrics file for the font

* embedding-mode: subset (default) or full

* kerning: yes or no

* style: normal or italic

* weight: normal or bold

Example: Assume the font Times that have three variants: normal, bold and italic. Then construct the following namespaces:

Skribenta.Publish.PDF.Fonts.Times.Normal

Skribenta.Publish.PDF.Fonts.Times.Bold

Skribenta.Publish.PDF.Fonts.Times.Italic

In each ns, add a variable table with the attributes above. E.g., an embed-url for the Bold variant would point to a corresponding font file containing the bold font. The attributes style and weight would be normal and bold, respectively.

763 FOP Improvements

FOP event listener added for improved logging for users. Some general improvements were also implemented.