freetype
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Freetype] TrueType glyph names


From: Ian Pilcher
Subject: [Freetype] TrueType glyph names
Date: Fri, 11 May 2001 13:59:55 -0500

I just noticed the following in ftoption.h:

 
/************************************************************************
  /*                                                           
  /* Glyph Postscript Names handling                         
  /*                                                      
  /*   By default, FreeType 2 is compiled with the `PSNames' module. 
This
  /*   This module is in charge of converting a glyph name string into a
  /*   Unicode value, or return a Macintosh standard glyph name for the
  /*   use with the TrueType `post' table.                             
  /*                                                               
  /*   Undefine this macro if you do not want `PSNames' compiled in your
  /*   build of FreeType.  This has the following effects:            
  /*                                                                
  /*   - The TrueType driver will provide its own set of glyph names, 
  /*     if you build it to support postscript names in the TrueType
  /*     `post' table.                                               
  /*                                                                  
  /*   - The Type 1 driver will not be able to synthetize a Unicode
  /*     charmap out of the glyphs found in the fonts.                 
  /*                                                                    
  /*   You would normally undefine this configuration macro when
building
  /*   a version of FreeType that doesn't contain a Type 1 or CFF
driver.
  /*                                                             
#define FT_CONFIG_OPTION_POSTSCRIPT_NAMES

I need to extract the glyph names that are actually contained in the
TrueType font.  My application will be widely distributed, so requiring
that the library be recompiled is not option.

Is there any way to meet this requirement?

Thanks!
-- 
========================================================================
Ian Pilcher                                         address@hidden
========================================================================



reply via email to

[Prev in Thread] Current Thread [Next in Thread]