Known Issues

• All versions prior to 0.5.0 have a problem displaying the properties of a TrueType font: if the license (found in the OpenType tab) text is too big, the window will also be too big.
  Newer versions put that text into an scrolling window.
• All versions prior to 0.5.0 generate, when viewing all glyphs of a font thorugh the font table window, a notebook with one tab for each group of 256 glyphs.
  This means that all glyphs are rendered after each other, and each tab creates an XWindow pixmap. It is clear that a big font (such as Unicode fonts) will take a long time to render and even run the X-Server out of resources, so that the program will probably crash.
  Version 0.5.0 only renders one group of 256 glyphs at a time.
• All versions prior to and including 0.5.0 generate Type 42 fonts which have problems with ghostscript 6.x.
  The problem lies within ghostscript, as gfontview generates fonts compliant to Adobe's specifications (Technical Note 5012). Specifically, the sfnts array consists of several strings:

                  /sfnts [ <string1> <string3> ... <stringN> ] def

  Each string must be terminated, according to Adobe, by an additional padding byte, "00", to be compatible with PostScript interpreter implementations prior to 2013.
  It seems ghostscript 6.x dropped support for this, so you have to manually delete that 00 from the generated PostScript or change the source code in the file tt.C, function write_string. Change the last line of that function (line 2371) from

  fputs("\n00>", ofp);

  to

  fputs("\n>", ofp);

  and recompile.
• Some fonts have no names for its glyphs. Or some, specially big Unicode fonts, name all of them /.notdef. They cannot be printed, as PostScript relies on all glyphs having a name. No known workaround.