Fonts

The following is the initial Font Configuration File. After you have finished the installation of Rainbow PDF Server Based Converter V3.0 Solaris / Linux version, this file will be located at [Install directory]/etc.

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

In Rainbow PDF Server Based Converter V3.0 Windows version, the following Font Configuration File is installed on [Install directory]. The Windows font directory is set to [System font directory].

<?xml version="1.0" encoding="UTF-8" ?>
<!-- DOCTYPE font-config SYSTEM "font-config.dtd" -->
<font-config>
  <name-processing-mode mode="windows-name"/>
  <font-folder path="[System font directory]">
  </font-folder>
</font-config>

In Windows version, when there is no Font Configration File, the Font Configration File of this content will be assumed.

The following table is a summary of the elements and attributes in the Font Configuration File.

<name-processing-mode mode="windows-name"/>

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

<glyph-list file="carta.txt" afm="CR______.AFM"/>

<skip-glyphname-mapping afm="CR______.AFM"/>

<font-exclude file="times.ttf"/>

<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" />

The DTD of Font Configuration File is as follows:

<!ELEMENT font-config ( name-processing-mode?, 
                        font-folder+,
                        windows-registry?, eudc-processing? ) >

<!ELEMENT name-processing-mode EMPTY >
<!ATTLIST name-processing-mode mode (default|windows-name) "default" >


<!ELEMENT font-folder ( glyph-list
                      | skip-glyphname-mapping
                      | font-exclude
                      | font-alias
                      )* >
<!ATTLIST font-folder path CDATA #REQUIRED >

<!ELEMENT glyph-list EMPTY >
<!ATTLIST glyph-list file CDATA #REQUIRED
                     afm  CDATA #REQUIRED >

<!ELEMENT skip-glyphname-mapping EMPTY >
<!ATTLIST skip-glyphname-mapping afm CDATA #IMPLIED
                                 pfm CDATA #IMPLIED >

<!ELEMENT font-exclude EMPTY >
<!ATTLIST font-exclude file CDATA #REQUIRED >

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

<!ELEMENT alias EMPTY >
<!ATTLIST alias family-name CDATA #REQUIRED
                weight (normal|bold|100|200|300|400|500|600|700|800|900) #IMPLIED
                italic (true|false) #IMPLIED >

<!ELEMENT windows-registry EMPTY >
<!ATTLIST windows-registry reference (enable|disable) #IMPLIED >

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

<!ELEMENT eudc-range EMPTY >
<!ATTLIST eudc-range start NUMBER #REQUIRED
                     end   NUMBER #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
                   file-path   CDATA #REQUIRED >

Adobe Type1 fonts are organized using the following font files.

Rainbow PDF Server Based Converter V3.0 supports both types of combinations: .AFM+.PFB, .PFM+.PFB files.

Type1 font considerations.

• The current version of Rainbow PDF Server Based Converter V3.0 does not support font outline files with .PFA (Printer Font ASCII) extension. Most Type1 font products are shipped in the .PFB format, which is supported by Rainbow PDF Server Based Converter V3.0.
• Type1 font metrics data which has the .MMM extension is not supported. This metrics file is used for the Multiple Master Type1 fonts.
• Both.PFB and .PFM that maps to .PFB must exist in the same directory. Fonts may be installed in different directories by using ATM (Adobe Type Manager). Such fonts cannot be used for embedding with Rainbow PDF Server Based Converter V3.0.

Rainbow PDF Server Based Converter V3.0 supports embedding the Type1 font into PDF files. The followings are required to embed fonts:

• The .AFM+.PFB or .PFM+.PFB font files must be in the folder specified in the <font-folder> of the font configuration file.

If you do not embed fonts, only .AFM or .PFM files are needed. If fonts are not embedded in the PDF the user will need the actual fonts on their system when they read the PDF file.

To use Adobe Type1 font with .AFM files, it is important to know how Unicode characters are mapped into Type1 font glyphs. The following is a brief explanation of how Type1 fonts are treated in PDF files.

• In the PDF file, letters which are associated with Type1 fonts are stored using 0..255 value character codes.
• Each Type1 font in the PDF file has the encoding parameters, which defines the character code to the corresponding glyph-name.
• The PDF reader application (typically Adobe Acrobat or Reader) converts the character codes to glyph-names using encoding parameters. Then reader then gets the Type1 glyph outline using the glyph-name as a key index. Finally the glyph is rendered using this outline data.

Example: if the encoding parameter of the Type1 font is Adobe Standard Encoding, and we want to write a "•" (U+2022 BULLET) to a PDF file, we must select character code 0xB7(183) because the glyph-name of this character is "bullet" and it is defined as 0xB7 in the Adobe Standard Encoding.

Before we can write a character code to the PDF file we must first get the glyph-name from the Unicode. This process is described in the Adobe web site document Unicode and Glyph Names. The most important mapping rule is described in AGL (Adobe Glyph List) file. AGL is a simple text file that defines the Unicode to glyph name mapping rules for over 800 Latin characters. Rainbow PDF Server Based Converter V3.0 uses this data to map the Unicode to glyph name. Following is a brief description of how Rainbow PDF Server Based Converter V3.0 maps the Unicode value to glyph name and writes a character code to the PDF file.

1. Rainbow PDF Server Based Converter V3.0 using the AGL data gets the glyph name from this Unicode character.
2. Consulting the .AFM file, determines the encoding parameter for this Type1 font.
3. Also consulting the .AFM file gets the character metrics information and character code from the glyph name.
4. Writes the obtained character code and encoding information to the PDF file.

If you are using Adobe Type1 fonts with .PFM files, Rainbow PDF Server Based Converter V3.0 maps Unicode to glyphs differently than above, which does not use glyph names.

First, .PFM file has the only one encoding data in the dfCharSet field of PFM header. This one byte field contains the value known as character set. In the Windows environment, there are following character sets are defined in WINGDI.H header file.

Microsoft mapping can be found at the Unicode to code page mapping data. Rainbow PDF Server Based Converter V3.0 uses this mapping data and converts the Unicode to the character code to write it to the PDF file. This mapping data has a maximum of 256 entries because the code page offers only 8-bit character width. You cannot use glyphs which are not defined in the code page data unless it exists in font the outline data.

As mentioned in Unicode and glyph mapping using the .AFM file, AGL offers the Unicode to glyph name mapping rules. It covers commonly used Latin characters. But there are special fonts which do not fit the AGL. For instance, the Adobe Type1 product Carta (CR______.AFM, CR______.PFM, CR______.PFB) has 189 pictorial glyphs and non-standard glyph names. If we look up the glyph names into the AGL, we will get the result that only 14-glyph names match and the others do not match with the AGL. If we leave it as it is, we cannot use most of the glyphs in the Carta with the .AFM+.PFB combination.

To solve such problem, Rainbow PDF Server Based Converter V3.0 offers two solutions. One is to make a glyph list file for this font. Another is to specify the <skip-glyphname-mapping> in the font configuration XML file.

Glyph list file

# Carta sample glyphlist file
# file name:carta-glyphname.txt
0020;space;
E000;circle;
E001;lookoutcontrol;
E002;triangle;
E003;diamond;
E004;hexagon;
E005;explode2;
E006;lookout;
E007;IRBM;
E008;ICBM;
E009;explode1;
E00A;ruin;
E00B;goldbar;
E00C;lighthouse;
E00D;mining;
E00E;gaging;
0030;zero;
0031;one;
0032;two;
0033;three;
0034;four;
0035;five;
0036;six;
0037;seven;
0038;eight;
0039;nine;
E00F;boundary;
...

<font-config>
  <font-folder path="[Install directory]/fonts">
    <glyph-list file="ZapfDingbats-glyphname.txt" afm="ZapfDingbats.afm"/>
  </font-folder>
  <font-folder path="/home/resource/fonts">
    <glyph-list file="carta-glyph-list.txt" afm="CR______.AFM"/>
  </font-folder>
</font-config>

Skipping the glyph name mapping

<font-config>
  <font-folder path="[Install directory]/fonts">
    <glyph-list file="zapfdingbats-glyphname.txt" afm="ZapfDingbats.afm"/>
  </font-folder>
  <font-folder path="/home/resource/fonts">
    <skip-glyphname-mapping afm="CR______.AFM"/>
  </font-folder>
</font-config>

EncodingScheme FontSpecific
StartCharMetrics 189
C 32 ; WX 280 ; N space ; B 0 0 0 0 ;
C 33 ; WX 560 ; N circle ; B 30 150 530 650 ;
C 34 ; WX 620 ; N lookoutcontrol ; B 15 60 605 741 ;
...
C 250 ; WX 1042 ; N boat ; B 30 0 1012 280 ;
C 251 ; WX 852 ; N portofentry ; B 30 123 822 677 ;
C 252 ; WX 946 ; N whwycounty ; B 0 -58 946 857 ;
C 253 ; WX 1154 ; N whwytridown ; B 0 -100 1154 899 ;
C 254 ; WX 1072 ; N whwytriright ; B 0 -121 1073 919 ;
EndCharMetrics

Some Type1 font family names are troublesome when installed. For instance, if you install Adobe product Eurostile Type1 font in .AFM+.PFB pair, there occurs a font selection problem depending on the font file combination. The following table describes the font family name problem for some font file combinations.

If you use these fonts with .PFM+.PFB combination, there are no problems because the .PFM file exposes all the different font family names. In contrast, if you install these fonts with .AFM+.PFB combination, all of the font family names are Eurostile only. Furthermore, there are plural fonts that have the same weight value. The Weight value Medium and Roman are interpreted as font-weight="400" and Bold is interpreted as font-weight="700".

To avoid this problem, define a new family name using the alias element in the font configuration file. The following example defines the .PFM with like family name alias.

<font-config>
  <font-folder path="[Install directory]/fonts">
    <glyph-list file="ZapfDingbats.txt" afm="ZapfDingbats.afm"/>
  </font-folder>
  <font-folder path="/home/resource/fonts">
    <!-- Set the family-name and weight to the PFM definition -->
    <font-alias  file="EU______.AFM">
      <alias family-name="Adobe Eurostile"/>
    </font-alias>
    <font-alias  file="EUB_____.AFM">
      <alias family-name="Adobe Eurostile Bold" weight="normal"/>
    </font-alias>
    <font-alias  file="EUEX____.AFM">
      <alias family-name="Adobe Eurostile ExtendedTwo"/>
    </font-alias>
    <font-alias  file="EUBEX___.AFM">
      <alias family-name="Adobe Eurostile ExtendedTwo" weight="bold"/>
    </font-alias>
  </font-folder>
</font-config>

Rainbow PDF Server Based Converter V3.0 Windows version can print the formatted results without generating a PDF file. Windows functionality is used to do this, thus the font usage is based on Windows. In other words, Windows accesses the fonts using WindowsName in the .PFM file. For this reason, there is a possibility mapping will fail if you use the FamilyName in the .AFM file. This problem can be avoided by specifying <name-processing-mode mode="windows-name"/> in the Font Configuration File. In this case you need to define the alias name for .AFM file because the .AFM file cannot be specified directly.

As a general rule Windows does not normally use/include the .AFM file, so this is not a common problem.

In non-Windows version, the following Adobe Type1 fonts are installed.

• Courier.afm
• Courier-Bold.afm
• Courier-Oblique.afm
• Courier-BoldOblique.afm
• Helvetica.afm
• Helvetica-Bold.afm
• Helvetica-Oblique.afm
• Helvetica-BoldOblique.afm
• Times-Roman.afm
• Times-Bold.afm
• Times-Italic.afm
• Times-BoldItalic.afm
• Symbol.afm
• ZapfDingbats.afm

Because .AFM or .PFM is not included in these, it is not possible to embed it in PDF. Please refer to the bundled MustRead.html before you use.

These fonts can be downloaded from PDF core font information.

TrueType fonts were originally developed by Apple Computer and have been used in the Windows environment. OpenType fonts were jointly developed by Adobe and Microsoft as cross-platform fonts. Due to the origin, OpenType fonts have two flavors/kinds. One has the TrueType outline. The other has the PostScript outline. OpenType font files that have the TrueType outline have the file extension .TTF or .TTC. OpenType font files that have the PostScript outline have the extension .OTF. This section treats original TrueType fonts and OpenType (TrueType outline) fonts together. From now on, we will use the term TrueType fonts as the contraction of TrueType font and OpenType (TrueType outline).

TrueType fonts are composed of a single file which has the extension .TTF or .TTC. TTC is the abbreviation of the TrueType Collection. It contains plural TrueType fonts in a single file structure. It is sometimes used in the CJK fonts.

TrueType font requirements:

• Font must have the cmap table which enables mapping the Unicode to glyph index. (Almost TrueType fonts have the cmap table available.)
• Some older TrueType fonts do not have Code Page information in the OS/2 table (ulCodePageRange1, 2) which can negatively influence Rainbow PDF Server Based Converter V3.0's font selection algorithms. For this reason we recommend not using old TrueType fonts.

Rainbow PDF Server Based Converter V3.0 supports embedding the TrueType font into PDF. One big difference is the embedding license. TrueType font has the license information in OS/2 table fsType field. Rainbow PDF Server Based Converter V3.0 respects this licensing information which will cause embedding errors when you specify font embedding against fonts with restrictions on embedding. In addition, only the used glyphs are embedded with the TrueType fonts.

OpenType (PostScript outline) is one flavor of OpenType fonts as described in Font organization and necessary condition. OpenType (PostScript outline) font files have an extension .OTF and consists of only a single file. In addition, OpenType(PostScript outline) is classified into two categories. One is OpenType (PostScript) CID font and the other is OpenType (PostScript) non-CID font. The following table gives a brief description of these categories.

OpenType is a new format standard requiring no special conditions to use it from Rainbow PDF Server Based Converter V3.0.

The usage and family-name, font-weight, font-style mapping conditions are the same as for TrueType fonts. Please refer to the Font organization and necessary condition for details.

Some OpenType (PostScript outline) has the font-weight value which is not a multiple of 100. Rainbow PDF Server Based Converter V3.0 round off the font-weight value.

Font embedding is the same as for TrueType fonts. Please refer to the Embedding TrueType fonts for details.

Some OpenType (PostScript outline) CID fonts have a family name defined per font file. Originally these fonts belonged to the same family and each font file has a different font-weight value.

In the Windows environment it is not allowed to have more than three weight-values in the same family name. (Macintosh does allows such combinations.) As a result, these fonts have different family name per font file. This makes it inconvenient to use these fonts using the different family name. To integrate the family names, the following alias descriptions to the font configuration file should be added.

<font-config>
  <font-folder path="[Install directory]/fonts">
    <glyph-list file="ZapfDingbats.txt" afm="ZapfDingbats.afm"/>
  </font-folder>
  <font-folder path="/home/resource/fonts">
    <!-- Integrate the four OTF font's family name to
         "Heisei Kaku Gothic Std"-->
    <font-alias  file="HeiseiKakuGoStd-W3.otf">
      <alias family-name="Heisei Kaku Gothic Std" weight="300" />
    </font-alias>
    <font-alias  file="HeiseiKakuGoStd-W5.otf">
      <alias family-name="Heisei Kaku Gothic Std" weight="500" />
    </font-alias>
    <font-alias  file="HeiseiKakuGoStd-W7.otf">
      <alias family-name="Heisei Kaku Gothic Std" weight="700" />
    </font-alias>
    <font-alias  file="HeiseiKakuGoStd-W9.otf">
      <alias family-name="Heisei Kaku Gothic Std" weight="900" />
    </font-alias>
  </font-folder>
</font-config>