Import freetype 2.2.1

1 files changed, 15 insertions, 15 deletions

diff --git a/lib/freetype/docs/CUSTOMIZE b/lib/freetype/docs/CUSTOMIZE
index 7d7d474ec..0fe3f47b8 100644
--- a/lib/freetype/docs/CUSTOMIZE
+++ b/lib/freetype/docs/CUSTOMIZE
@@ -12,16 +12,16 @@ I. Configuration macros
   list  of  commented configuration  macros  that  can  be toggled  by
   developers  to  indicate  which  features  should  be  active  while
   building the library.
-
+  
   These  options range  from debug  level to  availability  of certain
   features,   like  native   TrueType  hinting   through   a  bytecode
   interpreter.
-
+  
   We  invite you  to read  this file  for more  information.   You can
   change the  file's content to suit  your needs, or  override it with
   one of the techniques described below.
 
-
+  
 II. Modules list
 
   If you  use GNU make  please edit the top-level  file `modules.cfg'.
@@ -43,7 +43,7 @@ III. System interface
   FreeType's  default interface to  the system  (i.e., the  parts that
   deal  with  memory  management   and  i/o  streams)  is  located  in
   `src/base/ftsystem.c'.
-
+  
   The current  implementation uses standard C library  calls to manage
   memory  and to read  font files.   It is  however possible  to write
   custom implementations to suit specific systems.
@@ -51,21 +51,21 @@ III. System interface
   To  tell the  GNU Make-based  build system  to use  a  custom system
   interface, you have to  define the environment variable FTSYS_SRC to
   point to the relevant implementation:
-
+  
     on Unix:
 
       ./configure <your options>
       export FTSYS_SRC=foo/my_ftsystem.c
       make
       make install
-
+   
     on Windows:
 
       make setup <compiler>
       set FTSYS_SRC=foo/my_ftsystem.c
       make
-
-
+     
+     
 IV. Overriding default configuration and module headers
 
   It  is possible  to override  the default  configuration  and module
@@ -84,10 +84,10 @@ IV. Overriding default configuration and module headers
 
 
   2. Using the C include path
-
+  
     Use the  C include path  to ensure that  your own versions  of the
     files are used at compile time when the lines
-
+    
       #include FT_CONFIG_OPTIONS_H
       #include FT_CONFIG_MODULES_H
 
@@ -100,7 +100,7 @@ IV. Overriding default configuration and module headers
           config/
             ftoption.h    => custom options header
             ftmodule.h    => custom modules list
-
+             
       include/            => normal FreeType 2 include
         freetype/
           ...
@@ -110,11 +110,11 @@ IV. Overriding default configuration and module headers
 
 
   3. Redefining FT_CONFIG_OPTIONS_H and FT_CONFIG_MODULES_H
-
+  
     Another way to do the same thing is to redefine the macros used to
     name  the configuration  headers.  To  do  so, you  need a  custom
     `ft2build.h' whose content can be as simple as:
-
+   
       #ifndef __FT2_BUILD_MY_PLATFORM_H__
       #define __FT2_BUILD_MY_PLATFORM_H__
 
@@ -124,9 +124,9 @@ IV. Overriding default configuration and module headers
       #include <freetype/config/ftheader.h>
 
       #endif /* __FT2_BUILD_MY_PLATFORM_H__ */
-
+   
     Place those files in a separate directory, e.g.,
-
+   
       custom/
         ft2build.h           => custom version described above
         my-ftoption.h        => custom options header