Development status: alpha
Added a new parser based on TTFontsUni PHP class from Ian Back (mPDF)
Added support for the newer dompdf_font_family_cache format
Fixed code order error which prevented processing of any fonts.
Added additional error checks to avoid sending unusable files back to the user.
Uses DOMPDF 0.6.0 beta 1 in order to be compatible with current public releases
Added tar.gz compression option
Using content buffering to try and avoid archive file corruption
When using the PHP-based font parser (ttf2ufm.php) no AFM files are produced. It is recommended that you enable Unicode support in DOMPDF when using this parser.
When using the PHP-based font parser (ttf2ufm.php) the font metrics do not include BBox values.
When using the PHP-based font parser (ttf2ufm.php) the font metrics use Unicode codes instead of the font-defined friendly names for characters.
When using the binary font parser (ttf2ufm) the amount of memory required may exceeed available resources, resulting in zero-byte font metrics files (and an error message stating that your font could not be processed)
Sometimes dompdf_font_family_cache is inserted in plain text at the front of the archive file
In order to use fonts outside the core PDF fonts you first have to "install" them into DOMPDF. If you find yourself having trouble with this process you can use this tool to generate the files you will need to do so.
After you submit your font files for processing your browser will download an archive file. Copy
the contents of this archive to your DOMPDF fonts folder (typically located at dompdf/lib/fonts).
If you have not previously installed fonts, you can rename the file
dompdf_font_family_cache. If you have previously installed fonts you will need to copy
the relevant entry from the sample file into your copy of the
Once you have taken these steps your font should be installed and ready to use.
Please submit questions and/or feedback about this tool to the support group.