Fonts

This chapter explains about the fonts which Antenna House Formatter V7.4 supports and how to use them. Also it explains the general consideration for each type of font.

The Font Configuration File is for setting the details of the font environment. In non-Windows versions: Although the initial file is prepared, you need to set it in accordance with your font environment. In Windows versions: The font configuration file may be used as is.

Antenna House Formatter V7.4 also supports Adobe Fonts and EUDC (end user defined character) for Private Use Characters.

Antenna House Formatter V7.4 supports the following types of fonts.

• Type 1

  Type 1 font files usually consists of a pair of font files .AFM+.PFB or .PFM+.PFB. The former is used in non-Windows environment. The latter is used in Windows environment. For further information, see Type 1.

• TrueType

  TrueType font files have the .TTF or .TTC extension. For further information, see TrueType.

• OpenType

  OpenType font files have the .TTF or .OTF extension. Fonts with the .TTF extension are fonts that contain TrueType outline information and are treated the same as TrueType. See TrueType. Fonts with the .OTF extension are fonts that contain PostScript outline information. See OpenType. Supports also OpenType Collection.

• WOFF File Format 1.0 no-LT

  You can treat WOFF (Web Open Font Format) by specifying to <axf:font-face>. WOFF fonts cannot be specified directly. The WOFF font specified by <axf:font-face> is treated as a TrueType or an OpenType. It's not necessary to specify the place where the WOFF font is located in the Font Configuration File. These functions are not available with Antenna House Formatter V7.4 Lite.

• WOFF File Format 2.0 no-LT

  You can treat WOFF 2.0 as well as WOFF 1.0.

  CAUTION:	WOFF2, which is based on TrueType Collection, OpenType Collection, is not supported.

• Macintosh TrueType data fork suitcase

  Supports Macintosh TrueType Suitcase expressed by the .dfont extension or the .dfon extension. This is the Font Suitcase whose font is defined as the data fork. The old Font Suitcase, which is used by Classic MacOS and whose font is defined in the resource fork, is not supported. The contents is TrueType. For details, see also TrueType.

To configure the font environment for Antenna House Formatter V7.4, you must make a Font Configuration File.

The Font Configuration File is a simple structured XML file and is usually located in the [Install directory]/​etc on non-Windows and [Install directory] on Windows.

The Font Configuration File should be set in the Environment Variables. The name font-config.xml is set as default.

In the Font Configuration File, the most important element is <font-folder>. If you want to use more than the PDF Standard 14 Fonts on non-Windows, you must locate the font files and add their directory as a <font-folder path="..."> element to the configuration file.

Antenna House Formatter V7.4 automatically detects the font files in the specified directory at the <font-folder path="...">. However, there are a few cases where the font name cannot be resolved, only in such cases it is necessary to describe the font file. Normally it is not necessary to specify each file to be used.

When multiple <font-folder path="..."> contain fonts with the same name, the first one is used. For example, if you want to use a different version of a font than the one installed in Windows, specify the font-folder containing that font before the setting of @@WINFONTS@@.

In Windows versions, the default font configuration includes all the installed fonts in the Windows font directory. Antenna House Formatter V7.4 reads the information on the fonts available to use when running Antenna House Formatter V7.4. In other words, the more fonts that are present, the more processing time is taken. This means that it may take more time to initialize fonts than time to format when formatting a small document. With a big document, the time to initialize font may not be significant. In order to save the time to initialize fonts, reduce the available fonts. There are the following three solutions available:

1. Reduce the font installed in the Windows font directory.
2. In the Font Configuration File, enumerate fonts that are not used in the Windows font directory by using the font-exclude attribute.
3. Prepare the separate directory where only necessary fonts are included and specify only that directory in the Font Configuration File.

A realistic solution may probably be 3. For example, put fonts you'd like to use in the directory of C:\MyFonts and prepare the Font Configuration File like the following:

<?xml version="1.0" encoding="UTF-8" ?>
<font-config>
  <font-folder path="C:\MyFonts"/>
</font-config>

Be sure not to include the setting of Windows font directory here. Specify this Font Configuration File by the Environment Variables.

In Macintosh versions, the system font directory is also included in the Initial Font Configuration File. If necessary, adjust the Font Configuration File as well.

Initial Font Configuration File

<?xml version="1.0" encoding="UTF-8" ?>
<!-- DOCTYPE font-config SYSTEM "font-config.dtd" -->
<font-config>
  <!-- add your font folder here -->
  <!-- font-folder path="/home/user-name/fonts" -->
  <!-- /font-folder -->
  <font-folder path="@@HOME@@/fonts">
    <font-entry file="ZapfDingbats.afm"
          glyph-list="ZapfDingbats-glyphname.txt"/>
  </font-folder>
</font-config>

<?xml version="1.0" encoding="UTF-8" ?>
<!-- DOCTYPE font-config SYSTEM "font-config.dtd" -->
<font-config>
  <!-- add your font folder here -->
  <acc-folder path="@@ACCFOLDER@@"/>
  <font-folder path="/System/Library/Fonts"/>
  <font-folder path="/System/Library/Fonts/Supplemental"/>
  <font-folder path="/System/Library/Assets" recursive="true"/>
  <font-folder path="/System/Library/AssetsV2" recursive="true"/>
  <font-folder path="/Library/Fonts"/>
  <font-folder path="@@HOME@@/fonts">
    <font-entry file="ZapfDingbats.afm"
          glyph-list="ZapfDingbats-glyphname.txt"/>
  </font-folder>
</font-config>

<?xml version="1.0" encoding="UTF-8" ?>
<!-- DOCTYPE font-config SYSTEM "font-config.dtd" -->
<font-config>
  <!-- add your font folder here -->
  <acc-folder/>
  <font-folder path="@@USERWINFONTS@@"/>
  <font-folder path="@@WINFONTS@@"/>
</font-config>

Font Configuration File elements and attributes

<font-folder path="/home/user-name/fonts">
  ...
</font-folder>

<font-alias file="simsun.ttc" entry="1">
  ...
</font-alias>

<font-alias file="ARIALI.TTF">
  <alias family-name="MyArial"/>
</font-alias>
<font-alias file="ARIALBI.TTF">
  <alias family-name="MyArial" weight="bold"/>
</font-alias>

<eudc-range start="57344" end="63743"/>

<!ELEMENT font-config (font-folder+ | acc-folder? | eudc-processing?)>

<!ELEMENT font-folder (font-entry | font-alias)*>
<!ATTLIST font-folder path CDATA #REQUIRED>
<!ATTLIST font-folder recursive (true|false) #IMPLIED>

<!ELEMENT font-entry EMPTY>
<!ATTLIST font-entry file                   CDATA #REQUIRED>
<!ATTLIST font-entry glyph-list             CDATA #IMPLIED>
<!ATTLIST font-entry skip-glyphname-mapping (true|false) "false">
<!ATTLIST font-entry font-exclude           (true|false) "false">
<!ATTLIST font-entry unicode-range          CDATA "U+0-10FFFF">
<!ATTLIST font-entry font-size-adjust       CDATA "1.0">
<!ATTLIST font-entry baseline-adjust        CDATA "0.0">
<!ATTLIST font-entry x-height               CDATA "0.0">
<!ATTLIST font-entry cap-height             CDATA "0.0">

<!ELEMENT font-alias (alias)*>
<!ATTLIST font-alias file  CDATA #REQUIRED>
<!ATTLIST font-alias entry CDATA #IMPLIED>

<!ELEMENT alias EMPTY>
<!ATTLIST alias family-name CDATA   #REQUIRED>
<!ATTLIST alias weight      CDATA   #IMPLIED><!-- normal|bold|1..1000 -->
<!ATTLIST alias italic (true|false) #IMPLIED>

<!ELEMENT acc-folder EMPTY>
<!ATTLIST acc-folder path CDATA #IMPLIED>

<!ELEMENT eudc-processing (eudc-range?, eudc-system-default?, eudc-map*)>
<!ATTLIST eudc-processing mapping (enable|disable) #IMPLIED>

<!ELEMENT eudc-range EMPTY>
<!ATTLIST eudc-range start CDATA #REQUIRED>
<!ATTLIST eudc-range end   CDATA #IMPLIED>

<!ELEMENT eudc-system-default EMPTY>
<!ATTLIST eudc-system-default file-path CDATA #REQUIRED>

<!ELEMENT eudc-map EMPTY>
<!ATTLIST eudc-map family-name CDATA #REQUIRED>
<!ATTLIST eudc-map file-path   CDATA #REQUIRED>

This section describes general information for Type 1 fonts and how Antenna House Formatter V7.4 supports them.

Font organization and necessary condition

Embedding Type 1

PDF Standard 14 Fonts

This section describes Antenna House Formatter V7.4 implementation for TrueType and OpenType (TrueType outline) fonts. Tips on how to use these fonts in your environment are provided.

Font organization and necessary condition

Embedding TrueType

This section describes how Antenna House Formatter V7.4 implements OpenType (PostScript outline) fonts. Tips on how to use OpenType fonts more conveniently in your environment are provided. Hereafter, when simply saying OpenType in this document, it means OpenType of the PostScript outline.

Font organization and necessary condition

Embedding OpenType

Adobe Fonts is a font library service provided by Adobe. Antenna House Formatter V7.4 supports Adobe Fonts. For details on Adobe Fonts and available font licenses, see the following:

Adobe Fonts are available on Windows or Macintosh. To use Adobe Fonts, it is necessary to add the <acc-folder> element to the Font Configuration File in the environment where Adobe Fonts are installed. The Font Configuration File includes that setting by default.

In Windows, Adobe Fonts are installed in [APPDATA]\Adobe\CoreSync\plugins\livetype. [APPDATA] shows the location indicated by the environment variable. Specify it to the path of <acc-folder>. However, the path can be omitted in Windows versions. If the path is omitted and <acc-folder/> is specified, it is considered that it is specified as the path.

In Macintosh, Adobe Fonts are installed in ~/​Library/​Application Support/​Adobe/​CoreSync/​plugins/​livetype. Specify it to the path of <acc-folder>. It cannot be omitted.

Installed Adobe Fonts are OpenType. You can check the font family name, etc. in .../​livetype/​c/​entitlements.xml or .../​livetype/​.c/​entitlements.xml.

EUDC: End User Defined Character is available with Antenna House Formatter V7.4.

Since the information on EUDC is acquired from the registry, it is not necessary to create EUDC information to the Font Configuration File with Windows versions. However when EUDC information is described by the Font Configuration File, it is also taken into consideration. With non-Windows versions, it is necessary to create EUDC information to the Font Configuration File in order to use EUDC.

<font-config>
 <font-folder path="c:\Windows\Fonts"/>
 <eudc-processing mapping="enable">
  <eudc-range start="57344" end="63743"/>
  <eudc-system-default file-path="c:\Windows\Fonts\EUDC.TTE"/>
  <eudc-map family-name="MS Mincho" file-path="c:\Program Files\east\jinmei3\FEJPMIN.TTG"/>
  <eudc-map family-name="MS PMincho" file-path="c:\Program Files\east\jinmei3\FEJPMIN.TTG"/>
 </eudc-processing>
</font-config>

A user does not need to be conscious of utilizing EUDC. Antenna House Formatter V7.4 changes the font automatically by the character code.

There are V1 and V2 specifications for Indic OpenType Fonts. V2 is the specification published by Microsoft in 2008 and corresponds to the fonts included with Windows Vista or later. The main differences between V1 and V2 specifications are as follows:

• The script tag was changed.
• The way to divide text into syllables, which is the base of the text layout, was changed.
• The treatment of ZWJ, ZWNJ and NBSP used for the selection of the typeface was clearly defined.
• The behavior of consonant conjuncts or above-base vowel marks became font dependence.
• Features to be applied for GSUB and GPOS were added.
• The applying order of GSUB and GPOS features was changed.

Antenna House Formatter V7.4 integrates fonts based on the V1 specification. Many of fonts corresponding to the V2 specification are also included in the features of V1 specification. Fonts that only have the V2 compliant are not supported.

There are some known problems in the Indic fonts implementation with Antenna House Formatter V7.4.

• With Kokila V5.* included with Windows Vista or later, the processing of Vattu is not correct. For example, a sequence of U+0915 U+094D U+0930 will be rendered as shown in the image on the right, although it should be rendered as shown on the left.

  It seems that the processing of the V1-compliant font itself is not correct. Use V1.00, etc.

• Kalinga V5.* included with Windows Vista or later only includes the features of the V2 specification. Antenna House Formatter V7.4 conforms to the V1 specification, so this font cannot be handled correctly. We recommend to use the free Lohit font (Oriya). Lohit fonts are downloadable from the following site:

  • Lohit Fonts

The following is not the problem of Antenna House Formatter V7.4, hope you find it informative.

• The typeface of DaunPenh V5.* included with Windows Vista or later is designed to be very small. Therefore, the balance is not very good when European languages etc. are mixed. We recommend to use the free KhmerOS font. KhmerOS fonts are downloadable from the following site:

  • Khmer Software Initiative