|
|
@@ -1,933 +1,1014 @@
|
|
|
-/***************************************************************************/
|
|
|
-/* */
|
|
|
-/* ftoption.h */
|
|
|
-/* */
|
|
|
-/* User-selectable configuration macros (specification only). */
|
|
|
-/* */
|
|
|
-/* Copyright 1996-2016 by */
|
|
|
-/* David Turner, Robert Wilhelm, and Werner Lemberg. */
|
|
|
-/* */
|
|
|
-/* This file is part of the FreeType project, and may only be used, */
|
|
|
-/* modified, and distributed under the terms of the FreeType project */
|
|
|
-/* license, LICENSE.TXT. By continuing to use, modify, or distribute */
|
|
|
-/* this file you indicate that you have read the license and */
|
|
|
-/* understand and accept it fully. */
|
|
|
-/* */
|
|
|
-/***************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
-#ifndef FTOPTION_H_
|
|
|
-#define FTOPTION_H_
|
|
|
-
|
|
|
-
|
|
|
-#include <ft2build.h>
|
|
|
-
|
|
|
-
|
|
|
-FT_BEGIN_HEADER
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* USER-SELECTABLE CONFIGURATION MACROS */
|
|
|
- /* */
|
|
|
- /* This file contains the default configuration macro definitions for */
|
|
|
- /* a standard build of the FreeType library. There are three ways to */
|
|
|
- /* use this file to build project-specific versions of the library: */
|
|
|
- /* */
|
|
|
- /* - You can modify this file by hand, but this is not recommended in */
|
|
|
- /* cases where you would like to build several versions of the */
|
|
|
- /* library from a single source directory. */
|
|
|
- /* */
|
|
|
- /* - You can put a copy of this file in your build directory, more */
|
|
|
- /* precisely in `$BUILD/freetype/config/ftoption.h', where `$BUILD' */
|
|
|
- /* is the name of a directory that is included _before_ the FreeType */
|
|
|
- /* include path during compilation. */
|
|
|
- /* */
|
|
|
- /* The default FreeType Makefiles and Jamfiles use the build */
|
|
|
- /* directory `builds/<system>' by default, but you can easily change */
|
|
|
- /* that for your own projects. */
|
|
|
- /* */
|
|
|
- /* - Copy the file <ft2build.h> to `$BUILD/ft2build.h' and modify it */
|
|
|
- /* slightly to pre-define the macro FT_CONFIG_OPTIONS_H used to */
|
|
|
- /* locate this file during the build. For example, */
|
|
|
- /* */
|
|
|
- /* #define FT_CONFIG_OPTIONS_H <myftoptions.h> */
|
|
|
- /* #include <freetype/config/ftheader.h> */
|
|
|
- /* */
|
|
|
- /* will use `$BUILD/myftoptions.h' instead of this file for macro */
|
|
|
- /* definitions. */
|
|
|
- /* */
|
|
|
- /* Note also that you can similarly pre-define the macro */
|
|
|
- /* FT_CONFIG_MODULES_H used to locate the file listing of the modules */
|
|
|
- /* that are statically linked to the library at compile time. By */
|
|
|
- /* default, this file is <freetype/config/ftmodule.h>. */
|
|
|
- /* */
|
|
|
- /* We highly recommend using the third method whenever possible. */
|
|
|
- /* */
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
- /**** ****/
|
|
|
- /**** G E N E R A L F R E E T Y P E 2 C O N F I G U R A T I O N ****/
|
|
|
- /**** ****/
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* If you enable this configuration option, FreeType recognizes an */
|
|
|
- /* environment variable called `FREETYPE_PROPERTIES', which can be used */
|
|
|
- /* to control the various font drivers and modules. The controllable */
|
|
|
- /* properties are listed in the section `Controlling FreeType Modules' */
|
|
|
- /* in the reference's table of contents; currently there are properties */
|
|
|
- /* for the auto-hinter (file `ftautoh.h'), CFF (file `ftcffdrv.h'), and */
|
|
|
- /* TrueType (file `ftttdrv.h'). */
|
|
|
- /* */
|
|
|
- /* `FREETYPE_PROPERTIES' has the following syntax form (broken here into */
|
|
|
- /* multiple lines for better readability). */
|
|
|
- /* */
|
|
|
- /* <optional whitespace> */
|
|
|
- /* <module-name1> ':' */
|
|
|
- /* <property-name1> '=' <property-value1> */
|
|
|
- /* <whitespace> */
|
|
|
- /* <module-name2> ':' */
|
|
|
- /* <property-name2> '=' <property-value2> */
|
|
|
- /* ... */
|
|
|
- /* */
|
|
|
- /* Example: */
|
|
|
- /* */
|
|
|
- /* FREETYPE_PROPERTIES=truetype:interpreter-version=35 \ */
|
|
|
- /* cff:no-stem-darkening=1 \ */
|
|
|
- /* autofitter:warping=1 */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Uncomment the line below if you want to activate sub-pixel rendering */
|
|
|
- /* (a.k.a. LCD rendering, or ClearType) in this build of the library. */
|
|
|
- /* */
|
|
|
- /* Note that this feature is covered by several Microsoft patents */
|
|
|
- /* and should not be activated in any default build of the library. */
|
|
|
- /* */
|
|
|
- /* This macro has no impact on the FreeType API, only on its */
|
|
|
- /* _implementation_. For example, using FT_RENDER_MODE_LCD when calling */
|
|
|
- /* FT_Render_Glyph still generates a bitmap that is 3 times wider than */
|
|
|
- /* the original size in case this macro isn't defined; however, each */
|
|
|
- /* triplet of subpixels has R=G=B. */
|
|
|
- /* */
|
|
|
- /* This is done to allow FreeType clients to run unmodified, forcing */
|
|
|
- /* them to display normal gray-level anti-aliased glyphs. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Many compilers provide a non-ANSI 64-bit data type that can be used */
|
|
|
- /* by FreeType to speed up some computations. However, this will create */
|
|
|
- /* some problems when compiling the library in strict ANSI mode. */
|
|
|
- /* */
|
|
|
- /* For this reason, the use of 64-bit integers is normally disabled when */
|
|
|
- /* the __STDC__ macro is defined. You can however disable this by */
|
|
|
- /* defining the macro FT_CONFIG_OPTION_FORCE_INT64 here. */
|
|
|
- /* */
|
|
|
- /* For most compilers, this will only create compilation warnings when */
|
|
|
- /* building the library. */
|
|
|
- /* */
|
|
|
- /* ObNote: The compiler-specific 64-bit integers are detected in the */
|
|
|
- /* file `ftconfig.h' either statically or through the */
|
|
|
- /* `configure' script on supported platforms. */
|
|
|
- /* */
|
|
|
-#undef FT_CONFIG_OPTION_FORCE_INT64
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* If this macro is defined, do not try to use an assembler version of */
|
|
|
- /* performance-critical functions (e.g. FT_MulFix). You should only do */
|
|
|
- /* that to verify that the assembler function works properly, or to */
|
|
|
- /* execute benchmark tests of the various implementations. */
|
|
|
-/* #define FT_CONFIG_OPTION_NO_ASSEMBLER */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* If this macro is defined, try to use an inlined assembler version of */
|
|
|
- /* the `FT_MulFix' function, which is a `hotspot' when loading and */
|
|
|
- /* hinting glyphs, and which should be executed as fast as possible. */
|
|
|
- /* */
|
|
|
- /* Note that if your compiler or CPU is not supported, this will default */
|
|
|
- /* to the standard and portable implementation found in `ftcalc.c'. */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_INLINE_MULFIX
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* LZW-compressed file support. */
|
|
|
- /* */
|
|
|
- /* FreeType now handles font files that have been compressed with the */
|
|
|
- /* `compress' program. This is mostly used to parse many of the PCF */
|
|
|
- /* files that come with various X11 distributions. The implementation */
|
|
|
- /* uses NetBSD's `zopen' to partially uncompress the file on the fly */
|
|
|
- /* (see src/lzw/ftgzip.c). */
|
|
|
- /* */
|
|
|
- /* Define this macro if you want to enable this `feature'. */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_USE_LZW
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Gzip-compressed file support. */
|
|
|
- /* */
|
|
|
- /* FreeType now handles font files that have been compressed with the */
|
|
|
- /* `gzip' program. This is mostly used to parse many of the PCF files */
|
|
|
- /* that come with XFree86. The implementation uses `zlib' to */
|
|
|
- /* partially uncompress the file on the fly (see src/gzip/ftgzip.c). */
|
|
|
- /* */
|
|
|
- /* Define this macro if you want to enable this `feature'. See also */
|
|
|
- /* the macro FT_CONFIG_OPTION_SYSTEM_ZLIB below. */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_USE_ZLIB
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* ZLib library selection */
|
|
|
- /* */
|
|
|
- /* This macro is only used when FT_CONFIG_OPTION_USE_ZLIB is defined. */
|
|
|
- /* It allows FreeType's `ftgzip' component to link to the system's */
|
|
|
- /* installation of the ZLib library. This is useful on systems like */
|
|
|
- /* Unix or VMS where it generally is already available. */
|
|
|
- /* */
|
|
|
- /* If you let it undefined, the component will use its own copy */
|
|
|
- /* of the zlib sources instead. These have been modified to be */
|
|
|
- /* included directly within the component and *not* export external */
|
|
|
- /* function names. This allows you to link any program with FreeType */
|
|
|
- /* _and_ ZLib without linking conflicts. */
|
|
|
- /* */
|
|
|
- /* Do not #undef this macro here since the build system might define */
|
|
|
- /* it for certain configurations only. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_SYSTEM_ZLIB */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Bzip2-compressed file support. */
|
|
|
- /* */
|
|
|
- /* FreeType now handles font files that have been compressed with the */
|
|
|
- /* `bzip2' program. This is mostly used to parse many of the PCF */
|
|
|
- /* files that come with XFree86. The implementation uses `libbz2' to */
|
|
|
- /* partially uncompress the file on the fly (see src/bzip2/ftbzip2.c). */
|
|
|
- /* Contrary to gzip, bzip2 currently is not included and need to use */
|
|
|
- /* the system available bzip2 implementation. */
|
|
|
- /* */
|
|
|
- /* Define this macro if you want to enable this `feature'. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_USE_BZIP2 */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define to disable the use of file stream functions and types, FILE, */
|
|
|
- /* fopen() etc. Enables the use of smaller system libraries on embedded */
|
|
|
- /* systems that have multiple system libraries, some with or without */
|
|
|
- /* file stream support, in the cases where file stream support is not */
|
|
|
- /* necessary such as memory loading of font files. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_DISABLE_STREAM_SUPPORT */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* PNG bitmap support. */
|
|
|
- /* */
|
|
|
- /* FreeType now handles loading color bitmap glyphs in the PNG format. */
|
|
|
- /* This requires help from the external libpng library. Uncompressed */
|
|
|
- /* color bitmaps do not need any external libraries and will be */
|
|
|
- /* supported regardless of this configuration. */
|
|
|
- /* */
|
|
|
- /* Define this macro if you want to enable this `feature'. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_USE_PNG */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* HarfBuzz support. */
|
|
|
- /* */
|
|
|
- /* FreeType uses the HarfBuzz library to improve auto-hinting of */
|
|
|
- /* OpenType fonts. If available, many glyphs not directly addressable */
|
|
|
- /* by a font's character map will be hinted also. */
|
|
|
- /* */
|
|
|
- /* Define this macro if you want to enable this `feature'. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_USE_HARFBUZZ */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* DLL export compilation */
|
|
|
- /* */
|
|
|
- /* When compiling FreeType as a DLL, some systems/compilers need a */
|
|
|
- /* special keyword in front OR after the return type of function */
|
|
|
- /* declarations. */
|
|
|
- /* */
|
|
|
- /* Two macros are used within the FreeType source code to define */
|
|
|
- /* exported library functions: FT_EXPORT and FT_EXPORT_DEF. */
|
|
|
- /* */
|
|
|
- /* FT_EXPORT( return_type ) */
|
|
|
- /* */
|
|
|
- /* is used in a function declaration, as in */
|
|
|
- /* */
|
|
|
- /* FT_EXPORT( FT_Error ) */
|
|
|
- /* FT_Init_FreeType( FT_Library* alibrary ); */
|
|
|
- /* */
|
|
|
- /* */
|
|
|
- /* FT_EXPORT_DEF( return_type ) */
|
|
|
- /* */
|
|
|
- /* is used in a function definition, as in */
|
|
|
- /* */
|
|
|
- /* FT_EXPORT_DEF( FT_Error ) */
|
|
|
- /* FT_Init_FreeType( FT_Library* alibrary ) */
|
|
|
- /* { */
|
|
|
- /* ... some code ... */
|
|
|
- /* return FT_Err_Ok; */
|
|
|
- /* } */
|
|
|
- /* */
|
|
|
- /* You can provide your own implementation of FT_EXPORT and */
|
|
|
- /* FT_EXPORT_DEF here if you want. If you leave them undefined, they */
|
|
|
- /* will be later automatically defined as `extern return_type' to */
|
|
|
- /* allow normal compilation. */
|
|
|
- /* */
|
|
|
- /* Do not #undef these macros here since the build system might define */
|
|
|
- /* them for certain configurations only. */
|
|
|
- /* */
|
|
|
-/* #define FT_EXPORT(x) extern x */
|
|
|
-/* #define FT_EXPORT_DEF(x) x */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Glyph Postscript Names handling */
|
|
|
- /* */
|
|
|
- /* By default, FreeType 2 is compiled with the `psnames' module. 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 synthesize 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
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Postscript Names to Unicode Values support */
|
|
|
- /* */
|
|
|
- /* By default, FreeType 2 is built with the `PSNames' module compiled */
|
|
|
- /* in. Among other things, the module is used to convert a glyph name */
|
|
|
- /* into a Unicode value. This is especially useful in order to */
|
|
|
- /* synthesize on the fly a Unicode charmap from the CFF/Type 1 driver */
|
|
|
- /* through a big table named the `Adobe Glyph List' (AGL). */
|
|
|
- /* */
|
|
|
- /* Undefine this macro if you do not want the Adobe Glyph List */
|
|
|
- /* compiled in your `PSNames' module. The Type 1 driver will not be */
|
|
|
- /* able to synthesize a Unicode charmap out of the glyphs found in the */
|
|
|
- /* fonts. */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_ADOBE_GLYPH_LIST
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Support for Mac fonts */
|
|
|
- /* */
|
|
|
- /* Define this macro if you want support for outline fonts in Mac */
|
|
|
- /* format (mac dfont, mac resource, macbinary containing a mac */
|
|
|
- /* resource) on non-Mac platforms. */
|
|
|
- /* */
|
|
|
- /* Note that the `FOND' resource isn't checked. */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_MAC_FONTS
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Guessing methods to access embedded resource forks */
|
|
|
- /* */
|
|
|
- /* Enable extra Mac fonts support on non-Mac platforms (e.g. */
|
|
|
- /* GNU/Linux). */
|
|
|
- /* */
|
|
|
- /* Resource forks which include fonts data are stored sometimes in */
|
|
|
- /* locations which users or developers don't expected. In some cases, */
|
|
|
- /* resource forks start with some offset from the head of a file. In */
|
|
|
- /* other cases, the actual resource fork is stored in file different */
|
|
|
- /* from what the user specifies. If this option is activated, */
|
|
|
- /* FreeType tries to guess whether such offsets or different file */
|
|
|
- /* names must be used. */
|
|
|
- /* */
|
|
|
- /* Note that normal, direct access of resource forks is controlled via */
|
|
|
- /* the FT_CONFIG_OPTION_MAC_FONTS option. */
|
|
|
- /* */
|
|
|
-#ifdef FT_CONFIG_OPTION_MAC_FONTS
|
|
|
-#define FT_CONFIG_OPTION_GUESSING_EMBEDDED_RFORK
|
|
|
-#endif
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Allow the use of FT_Incremental_Interface to load typefaces that */
|
|
|
- /* contain no glyph data, but supply it via a callback function. */
|
|
|
- /* This is required by clients supporting document formats which */
|
|
|
- /* supply font data incrementally as the document is parsed, such */
|
|
|
- /* as the Ghostscript interpreter for the PostScript language. */
|
|
|
- /* */
|
|
|
-#define FT_CONFIG_OPTION_INCREMENTAL
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* The size in bytes of the render pool used by the scan-line converter */
|
|
|
- /* to do all of its work. */
|
|
|
- /* */
|
|
|
-#define FT_RENDER_POOL_SIZE 16384L
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* FT_MAX_MODULES */
|
|
|
- /* */
|
|
|
- /* The maximum number of modules that can be registered in a single */
|
|
|
- /* FreeType library object. 32 is the default. */
|
|
|
- /* */
|
|
|
-#define FT_MAX_MODULES 32
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Debug level */
|
|
|
- /* */
|
|
|
- /* FreeType can be compiled in debug or trace mode. In debug mode, */
|
|
|
- /* errors are reported through the `ftdebug' component. In trace */
|
|
|
- /* mode, additional messages are sent to the standard output during */
|
|
|
- /* execution. */
|
|
|
- /* */
|
|
|
- /* Define FT_DEBUG_LEVEL_ERROR to build the library in debug mode. */
|
|
|
- /* Define FT_DEBUG_LEVEL_TRACE to build it in trace mode. */
|
|
|
- /* */
|
|
|
- /* Don't define any of these macros to compile in `release' mode! */
|
|
|
- /* */
|
|
|
- /* Do not #undef these macros here since the build system might define */
|
|
|
- /* them for certain configurations only. */
|
|
|
- /* */
|
|
|
-/* #define FT_DEBUG_LEVEL_ERROR */
|
|
|
-/* #define FT_DEBUG_LEVEL_TRACE */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Autofitter debugging */
|
|
|
- /* */
|
|
|
- /* If FT_DEBUG_AUTOFIT is defined, FreeType provides some means to */
|
|
|
- /* control the autofitter behaviour for debugging purposes with global */
|
|
|
- /* boolean variables (consequently, you should *never* enable this */
|
|
|
- /* while compiling in `release' mode): */
|
|
|
- /* */
|
|
|
- /* _af_debug_disable_horz_hints */
|
|
|
- /* _af_debug_disable_vert_hints */
|
|
|
- /* _af_debug_disable_blue_hints */
|
|
|
- /* */
|
|
|
- /* Additionally, the following functions provide dumps of various */
|
|
|
- /* internal autofit structures to stdout (using `printf'): */
|
|
|
- /* */
|
|
|
- /* af_glyph_hints_dump_points */
|
|
|
- /* af_glyph_hints_dump_segments */
|
|
|
- /* af_glyph_hints_dump_edges */
|
|
|
- /* af_glyph_hints_get_num_segments */
|
|
|
- /* af_glyph_hints_get_segment_offset */
|
|
|
- /* */
|
|
|
- /* As an argument, they use another global variable: */
|
|
|
- /* */
|
|
|
- /* _af_debug_hints */
|
|
|
- /* */
|
|
|
- /* Please have a look at the `ftgrid' demo program to see how those */
|
|
|
- /* variables and macros should be used. */
|
|
|
- /* */
|
|
|
- /* Do not #undef these macros here since the build system might define */
|
|
|
- /* them for certain configurations only. */
|
|
|
- /* */
|
|
|
-/* #define FT_DEBUG_AUTOFIT */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Memory Debugging */
|
|
|
- /* */
|
|
|
- /* FreeType now comes with an integrated memory debugger that is */
|
|
|
- /* capable of detecting simple errors like memory leaks or double */
|
|
|
- /* deletes. To compile it within your build of the library, you */
|
|
|
- /* should define FT_DEBUG_MEMORY here. */
|
|
|
- /* */
|
|
|
- /* Note that the memory debugger is only activated at runtime when */
|
|
|
- /* when the _environment_ variable `FT2_DEBUG_MEMORY' is defined also! */
|
|
|
- /* */
|
|
|
- /* Do not #undef this macro here since the build system might define */
|
|
|
- /* it for certain configurations only. */
|
|
|
- /* */
|
|
|
-/* #define FT_DEBUG_MEMORY */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Module errors */
|
|
|
- /* */
|
|
|
- /* If this macro is set (which is _not_ the default), the higher byte */
|
|
|
- /* of an error code gives the module in which the error has occurred, */
|
|
|
- /* while the lower byte is the real error code. */
|
|
|
- /* */
|
|
|
- /* Setting this macro makes sense for debugging purposes only, since */
|
|
|
- /* it would break source compatibility of certain programs that use */
|
|
|
- /* FreeType 2. */
|
|
|
- /* */
|
|
|
- /* More details can be found in the files ftmoderr.h and fterrors.h. */
|
|
|
- /* */
|
|
|
-#undef FT_CONFIG_OPTION_USE_MODULE_ERRORS
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Position Independent Code */
|
|
|
- /* */
|
|
|
- /* If this macro is set (which is _not_ the default), FreeType2 will */
|
|
|
- /* avoid creating constants that require address fixups. Instead the */
|
|
|
- /* constants will be moved into a struct and additional intialization */
|
|
|
- /* code will be used. */
|
|
|
- /* */
|
|
|
- /* Setting this macro is needed for systems that prohibit address */
|
|
|
- /* fixups, such as BREW. [Note that standard compilers like gcc or */
|
|
|
- /* clang handle PIC generation automatically; you don't have to set */
|
|
|
- /* FT_CONFIG_OPTION_PIC, which is only necessary for very special */
|
|
|
- /* compilers.] */
|
|
|
- /* */
|
|
|
- /* Note that FT_CONFIG_OPTION_PIC support is not available for all */
|
|
|
- /* modules (see `modules.cfg' for a complete list). For building with */
|
|
|
- /* FT_CONFIG_OPTION_PIC support, do the following. */
|
|
|
- /* */
|
|
|
- /* 0. Clone the repository. */
|
|
|
- /* 1. Define FT_CONFIG_OPTION_PIC. */
|
|
|
- /* 2. Remove all subdirectories in `src' that don't have */
|
|
|
- /* FT_CONFIG_OPTION_PIC support. */
|
|
|
- /* 3. Comment out the corresponding modules in `modules.cfg'. */
|
|
|
- /* 4. Compile. */
|
|
|
- /* */
|
|
|
-/* #define FT_CONFIG_OPTION_PIC */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
- /**** ****/
|
|
|
- /**** S F N T D R I V E R C O N F I G U R A T I O N ****/
|
|
|
- /**** ****/
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_EMBEDDED_BITMAPS if you want to support */
|
|
|
- /* embedded bitmaps in all formats using the SFNT module (namely */
|
|
|
- /* TrueType & OpenType). */
|
|
|
- /* */
|
|
|
-#define TT_CONFIG_OPTION_EMBEDDED_BITMAPS
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_POSTSCRIPT_NAMES if you want to be able to */
|
|
|
- /* load and enumerate the glyph Postscript names in a TrueType or */
|
|
|
- /* OpenType file. */
|
|
|
- /* */
|
|
|
- /* Note that when you do not compile the `PSNames' module by undefining */
|
|
|
- /* the above FT_CONFIG_OPTION_POSTSCRIPT_NAMES, the `sfnt' module will */
|
|
|
- /* contain additional code used to read the PS Names table from a font. */
|
|
|
- /* */
|
|
|
- /* (By default, the module uses `PSNames' to extract glyph names.) */
|
|
|
- /* */
|
|
|
-#define TT_CONFIG_OPTION_POSTSCRIPT_NAMES
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_SFNT_NAMES if your applications need to */
|
|
|
- /* access the internal name table in a SFNT-based format like TrueType */
|
|
|
- /* or OpenType. The name table contains various strings used to */
|
|
|
- /* describe the font, like family name, copyright, version, etc. It */
|
|
|
- /* does not contain any glyph name though. */
|
|
|
- /* */
|
|
|
- /* Accessing SFNT names is done through the functions declared in */
|
|
|
- /* `ftsnames.h'. */
|
|
|
- /* */
|
|
|
-#define TT_CONFIG_OPTION_SFNT_NAMES
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* TrueType CMap support */
|
|
|
- /* */
|
|
|
- /* Here you can fine-tune which TrueType CMap table format shall be */
|
|
|
- /* supported. */
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_0
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_2
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_4
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_6
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_8
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_10
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_12
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_13
|
|
|
-#define TT_CONFIG_CMAP_FORMAT_14
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
- /**** ****/
|
|
|
- /**** T R U E T Y P E D R I V E R C O N F I G U R A T I O N ****/
|
|
|
- /**** ****/
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_BYTECODE_INTERPRETER if you want to compile */
|
|
|
- /* a bytecode interpreter in the TrueType driver. */
|
|
|
- /* */
|
|
|
- /* By undefining this, you will only compile the code necessary to load */
|
|
|
- /* TrueType glyphs without hinting. */
|
|
|
- /* */
|
|
|
- /* Do not #undef this macro here, since the build system might */
|
|
|
- /* define it for certain configurations only. */
|
|
|
- /* */
|
|
|
-#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_SUBPIXEL_HINTING if you want to compile */
|
|
|
- /* subpixel hinting support into the TrueType driver. This modifies the */
|
|
|
- /* TrueType hinting mechanism when anything but FT_RENDER_MODE_MONO is */
|
|
|
- /* requested. */
|
|
|
- /* */
|
|
|
- /* In particular, it modifies the bytecode interpreter to interpret (or */
|
|
|
- /* not) instructions in a certain way so that all TrueType fonts look */
|
|
|
- /* like they do in a Windows ClearType (DirectWrite) environment. See */
|
|
|
- /* [1] for a technical overview on what this means. See `ttinterp.h' */
|
|
|
- /* for more details on the LEAN option. */
|
|
|
- /* */
|
|
|
- /* There are three options. */
|
|
|
- /* */
|
|
|
- /* 1. This option is associated with the `Infinality' moniker. */
|
|
|
- /* Contributed by an individual nicknamed Infinality with the goal of */
|
|
|
- /* making TrueType fonts render better than on Windows. A high */
|
|
|
- /* amount of configurability and flexibility, down to rules for */
|
|
|
- /* single glyphs in fonts, but also very slow. Its experimental and */
|
|
|
- /* slow nature and the original developer losing interest meant that */
|
|
|
- /* this option was never enabled in default builds. */
|
|
|
- /* */
|
|
|
- /* 2. The new default mode for the TrueType driver. The Infinality code */
|
|
|
- /* base was stripped to the bare minimum and all configurability */
|
|
|
- /* removed in the name of speed and simplicity. The configurability */
|
|
|
- /* was mainly aimed at legacy fonts like Arial, Times New Roman, or */
|
|
|
- /* Courier. Legacy fonts are fonts that modify vertical stems to */
|
|
|
- /* achieve clean black-and-white bitmaps. The new mode focuses on */
|
|
|
- /* applying a minimal set of rules to all fonts indiscriminately so */
|
|
|
- /* that modern and web fonts render well while legacy fonts render */
|
|
|
- /* okay. */
|
|
|
- /* */
|
|
|
- /* 3. Compile both. */
|
|
|
- /* */
|
|
|
- /* By undefining these, you get rendering behavior like on Windows */
|
|
|
- /* without ClearType, i.e., Windows XP without ClearType enabled and */
|
|
|
- /* Win9x (interpreter version v35). Or not, depending on how much */
|
|
|
- /* hinting blood and testing tears the font designer put into a given */
|
|
|
- /* font. If you define one or both subpixel hinting options, you can */
|
|
|
- /* switch between between v35 and the ones you define. */
|
|
|
- /* */
|
|
|
- /* This option requires TT_CONFIG_OPTION_BYTECODE_INTERPRETER to be */
|
|
|
- /* defined. */
|
|
|
- /* */
|
|
|
- /* [1] http://www.microsoft.com/typography/cleartype/truetypecleartype.aspx */
|
|
|
- /* */
|
|
|
-/* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING 1 */
|
|
|
-#define TT_CONFIG_OPTION_SUBPIXEL_HINTING 2
|
|
|
-/* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING ( 1 | 2 ) */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED to compile the */
|
|
|
- /* TrueType glyph loader to use Apple's definition of how to handle */
|
|
|
- /* component offsets in composite glyphs. */
|
|
|
- /* */
|
|
|
- /* Apple and MS disagree on the default behavior of component offsets */
|
|
|
- /* in composites. Apple says that they should be scaled by the scaling */
|
|
|
- /* factors in the transformation matrix (roughly, it's more complex) */
|
|
|
- /* while MS says they should not. OpenType defines two bits in the */
|
|
|
- /* composite flags array which can be used to disambiguate, but old */
|
|
|
- /* fonts will not have them. */
|
|
|
- /* */
|
|
|
- /* http://www.microsoft.com/typography/otspec/glyf.htm */
|
|
|
- /* https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6glyf.html */
|
|
|
- /* */
|
|
|
-#undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_GX_VAR_SUPPORT if you want to include */
|
|
|
- /* support for Apple's distortable font technology (fvar, gvar, cvar, */
|
|
|
- /* and avar tables). This has many similarities to Type 1 Multiple */
|
|
|
- /* Masters support. */
|
|
|
- /* */
|
|
|
-#define TT_CONFIG_OPTION_GX_VAR_SUPPORT
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define TT_CONFIG_OPTION_BDF if you want to include support for */
|
|
|
- /* an embedded `BDF ' table within SFNT-based bitmap formats. */
|
|
|
- /* */
|
|
|
-#define TT_CONFIG_OPTION_BDF
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Option TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES controls the maximum */
|
|
|
- /* number of bytecode instructions executed for a single run of the */
|
|
|
- /* bytecode interpreter, needed to prevent infinite loops. You don't */
|
|
|
- /* want to change this except for very special situations (e.g., making */
|
|
|
- /* a library fuzzer spend less time to handle broken fonts). */
|
|
|
- /* */
|
|
|
- /* It is not expected that this value is ever modified by a configuring */
|
|
|
- /* script; instead, it gets surrounded with #ifndef ... #endif so that */
|
|
|
- /* the value can be set as a preprocessor option on the compiler's */
|
|
|
- /* command line. */
|
|
|
- /* */
|
|
|
-#ifndef TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES
|
|
|
-#define TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES 1000000L
|
|
|
-#endif
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
- /**** ****/
|
|
|
- /**** T Y P E 1 D R I V E R C O N F I G U R A T I O N ****/
|
|
|
- /**** ****/
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* T1_MAX_DICT_DEPTH is the maximum depth of nest dictionaries and */
|
|
|
- /* arrays in the Type 1 stream (see t1load.c). A minimum of 4 is */
|
|
|
- /* required. */
|
|
|
- /* */
|
|
|
-#define T1_MAX_DICT_DEPTH 5
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* T1_MAX_SUBRS_CALLS details the maximum number of nested sub-routine */
|
|
|
- /* calls during glyph loading. */
|
|
|
- /* */
|
|
|
-#define T1_MAX_SUBRS_CALLS 16
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* T1_MAX_CHARSTRING_OPERANDS is the charstring stack's capacity. A */
|
|
|
- /* minimum of 16 is required. */
|
|
|
- /* */
|
|
|
- /* The Chinese font MingTiEG-Medium (CNS 11643 character set) needs 256. */
|
|
|
- /* */
|
|
|
-#define T1_MAX_CHARSTRINGS_OPERANDS 256
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define this configuration macro if you want to prevent the */
|
|
|
- /* compilation of `t1afm', which is in charge of reading Type 1 AFM */
|
|
|
- /* files into an existing face. Note that if set, the T1 driver will be */
|
|
|
- /* unable to produce kerning distances. */
|
|
|
- /* */
|
|
|
-#undef T1_CONFIG_OPTION_NO_AFM
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Define this configuration macro if you want to prevent the */
|
|
|
- /* compilation of the Multiple Masters font support in the Type 1 */
|
|
|
- /* driver. */
|
|
|
- /* */
|
|
|
-#undef T1_CONFIG_OPTION_NO_MM_SUPPORT
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
- /**** ****/
|
|
|
- /**** C F F D R I V E R C O N F I G U R A T I O N ****/
|
|
|
- /**** ****/
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Using CFF_CONFIG_OPTION_DARKENING_PARAMETER_{X,Y}{1,2,3,4} it is */
|
|
|
- /* possible to set up the default values of the four control points that */
|
|
|
- /* define the stem darkening behaviour of the (new) CFF engine. For */
|
|
|
- /* more details please read the documentation of the */
|
|
|
- /* `darkening-parameters' property of the cff driver module (file */
|
|
|
- /* `ftcffdrv.h'), which allows the control at run-time. */
|
|
|
- /* */
|
|
|
- /* Do *not* undefine these macros! */
|
|
|
- /* */
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 500
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 400
|
|
|
-
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 1000
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 275
|
|
|
-
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 1667
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 275
|
|
|
-
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 2333
|
|
|
-#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 0
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* CFF_CONFIG_OPTION_OLD_ENGINE controls whether the pre-Adobe CFF */
|
|
|
- /* engine gets compiled into FreeType. If defined, it is possible to */
|
|
|
- /* switch between the two engines using the `hinting-engine' property of */
|
|
|
- /* the cff driver module. */
|
|
|
- /* */
|
|
|
-/* #define CFF_CONFIG_OPTION_OLD_ENGINE */
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
- /**** ****/
|
|
|
- /**** A U T O F I T M O D U L E C O N F I G U R A T I O N ****/
|
|
|
- /**** ****/
|
|
|
- /*************************************************************************/
|
|
|
- /*************************************************************************/
|
|
|
-
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Compile autofit module with CJK (Chinese, Japanese, Korean) script */
|
|
|
- /* support. */
|
|
|
- /* */
|
|
|
-#define AF_CONFIG_OPTION_CJK
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Compile autofit module with Indic script support. */
|
|
|
- /* */
|
|
|
-#define AF_CONFIG_OPTION_INDIC
|
|
|
-
|
|
|
- /*************************************************************************/
|
|
|
- /* */
|
|
|
- /* Compile autofit module with warp hinting. The idea of the warping */
|
|
|
- /* code is to slightly scale and shift a glyph within a single dimension */
|
|
|
- /* so that as much of its segments are aligned (more or less) on the */
|
|
|
- /* grid. To find out the optimal scaling and shifting value, various */
|
|
|
- /* parameter combinations are tried and scored. */
|
|
|
- /* */
|
|
|
- /* This experimental option is active only if the rendering mode is */
|
|
|
- /* FT_RENDER_MODE_LIGHT; you can switch warping on and off with the */
|
|
|
- /* `warping' property of the auto-hinter (see file `ftautoh.h' for more */
|
|
|
- /* information; by default it is switched off). */
|
|
|
- /* */
|
|
|
-#define AF_CONFIG_OPTION_USE_WARPER
|
|
|
-
|
|
|
- /* */
|
|
|
-
|
|
|
-
|
|
|
- /*
|
|
|
- * This macro is obsolete. Support has been removed in FreeType
|
|
|
- * version 2.5.
|
|
|
- */
|
|
|
-/* #define FT_CONFIG_OPTION_OLD_INTERNALS */
|
|
|
-
|
|
|
-
|
|
|
- /*
|
|
|
- * This macro is defined if native TrueType hinting is requested by the
|
|
|
- * definitions above.
|
|
|
- */
|
|
|
-#ifdef TT_CONFIG_OPTION_BYTECODE_INTERPRETER
|
|
|
-#define TT_USE_BYTECODE_INTERPRETER
|
|
|
-
|
|
|
-#if TT_CONFIG_OPTION_SUBPIXEL_HINTING & 1
|
|
|
-#define TT_SUPPORT_SUBPIXEL_HINTING_INFINALITY
|
|
|
-#endif
|
|
|
-
|
|
|
-#if TT_CONFIG_OPTION_SUBPIXEL_HINTING & 2
|
|
|
-#define TT_SUPPORT_SUBPIXEL_HINTING_MINIMAL
|
|
|
-#endif
|
|
|
-#endif
|
|
|
-
|
|
|
-
|
|
|
- /*
|
|
|
- * Check CFF darkening parameters. The checks are the same as in function
|
|
|
- * `cff_property_set' in file `cffdrivr.c'.
|
|
|
- */
|
|
|
-#if CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 < 0 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 < 0 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 < 0 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 < 0 || \
|
|
|
- \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 < 0 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 < 0 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 < 0 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 < 0 || \
|
|
|
- \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 > \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 > \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 > \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 || \
|
|
|
- \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 > 500 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 > 500 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 > 500 || \
|
|
|
- CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 > 500
|
|
|
-#error "Invalid CFF darkening parameters!"
|
|
|
-#endif
|
|
|
-
|
|
|
-FT_END_HEADER
|
|
|
-
|
|
|
-
|
|
|
-#endif /* FTOPTION_H_ */
|
|
|
-
|
|
|
-
|
|
|
-/* END */
|
|
|
+/****************************************************************************
|
|
|
+ *
|
|
|
+ * ftoption.h
|
|
|
+ *
|
|
|
+ * User-selectable configuration macros (specification only).
|
|
|
+ *
|
|
|
+ * Copyright (C) 1996-2023 by
|
|
|
+ * David Turner, Robert Wilhelm, and Werner Lemberg.
|
|
|
+ *
|
|
|
+ * This file is part of the FreeType project, and may only be used,
|
|
|
+ * modified, and distributed under the terms of the FreeType project
|
|
|
+ * license, LICENSE.TXT. By continuing to use, modify, or distribute
|
|
|
+ * this file you indicate that you have read the license and
|
|
|
+ * understand and accept it fully.
|
|
|
+ *
|
|
|
+ */
|
|
|
+
|
|
|
+
|
|
|
+#ifndef FTOPTION_H_
|
|
|
+#define FTOPTION_H_
|
|
|
+
|
|
|
+
|
|
|
+#include <ft2build.h>
|
|
|
+
|
|
|
+
|
|
|
+FT_BEGIN_HEADER
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * USER-SELECTABLE CONFIGURATION MACROS
|
|
|
+ *
|
|
|
+ * This file contains the default configuration macro definitions for a
|
|
|
+ * standard build of the FreeType library. There are three ways to use
|
|
|
+ * this file to build project-specific versions of the library:
|
|
|
+ *
|
|
|
+ * - You can modify this file by hand, but this is not recommended in
|
|
|
+ * cases where you would like to build several versions of the library
|
|
|
+ * from a single source directory.
|
|
|
+ *
|
|
|
+ * - You can put a copy of this file in your build directory, more
|
|
|
+ * precisely in `$BUILD/freetype/config/ftoption.h`, where `$BUILD` is
|
|
|
+ * the name of a directory that is included _before_ the FreeType include
|
|
|
+ * path during compilation.
|
|
|
+ *
|
|
|
+ * The default FreeType Makefiles use the build directory
|
|
|
+ * `builds/<system>` by default, but you can easily change that for your
|
|
|
+ * own projects.
|
|
|
+ *
|
|
|
+ * - Copy the file <ft2build.h> to `$BUILD/ft2build.h` and modify it
|
|
|
+ * slightly to pre-define the macro `FT_CONFIG_OPTIONS_H` used to locate
|
|
|
+ * this file during the build. For example,
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * #define FT_CONFIG_OPTIONS_H <myftoptions.h>
|
|
|
+ * #include <freetype/config/ftheader.h>
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ * will use `$BUILD/myftoptions.h` instead of this file for macro
|
|
|
+ * definitions.
|
|
|
+ *
|
|
|
+ * Note also that you can similarly pre-define the macro
|
|
|
+ * `FT_CONFIG_MODULES_H` used to locate the file listing of the modules
|
|
|
+ * that are statically linked to the library at compile time. By
|
|
|
+ * default, this file is `<freetype/config/ftmodule.h>`.
|
|
|
+ *
|
|
|
+ * We highly recommend using the third method whenever possible.
|
|
|
+ *
|
|
|
+ */
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** G E N E R A L F R E E T Y P E 2 C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+
|
|
|
+ /*#************************************************************************
|
|
|
+ *
|
|
|
+ * If you enable this configuration option, FreeType recognizes an
|
|
|
+ * environment variable called `FREETYPE_PROPERTIES`, which can be used to
|
|
|
+ * control the various font drivers and modules. The controllable
|
|
|
+ * properties are listed in the section @properties.
|
|
|
+ *
|
|
|
+ * You have to undefine this configuration option on platforms that lack
|
|
|
+ * the concept of environment variables (and thus don't have the `getenv`
|
|
|
+ * function), for example Windows CE.
|
|
|
+ *
|
|
|
+ * `FREETYPE_PROPERTIES` has the following syntax form (broken here into
|
|
|
+ * multiple lines for better readability).
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * <optional whitespace>
|
|
|
+ * <module-name1> ':'
|
|
|
+ * <property-name1> '=' <property-value1>
|
|
|
+ * <whitespace>
|
|
|
+ * <module-name2> ':'
|
|
|
+ * <property-name2> '=' <property-value2>
|
|
|
+ * ...
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ * Example:
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * FREETYPE_PROPERTIES=truetype:interpreter-version=35 \
|
|
|
+ * cff:no-stem-darkening=1
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Uncomment the line below if you want to activate LCD rendering
|
|
|
+ * technology similar to ClearType in this build of the library. This
|
|
|
+ * technology triples the resolution in the direction color subpixels. To
|
|
|
+ * mitigate color fringes inherent to this technology, you also need to
|
|
|
+ * explicitly set up LCD filtering.
|
|
|
+ *
|
|
|
+ * When this macro is not defined, FreeType offers alternative LCD
|
|
|
+ * rendering technology that produces excellent output.
|
|
|
+ */
|
|
|
+/* #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Many compilers provide a non-ANSI 64-bit data type that can be used by
|
|
|
+ * FreeType to speed up some computations. However, this will create some
|
|
|
+ * problems when compiling the library in strict ANSI mode.
|
|
|
+ *
|
|
|
+ * For this reason, the use of 64-bit integers is normally disabled when
|
|
|
+ * the `__STDC__` macro is defined. You can however disable this by
|
|
|
+ * defining the macro `FT_CONFIG_OPTION_FORCE_INT64` here.
|
|
|
+ *
|
|
|
+ * For most compilers, this will only create compilation warnings when
|
|
|
+ * building the library.
|
|
|
+ *
|
|
|
+ * ObNote: The compiler-specific 64-bit integers are detected in the
|
|
|
+ * file `ftconfig.h` either statically or through the `configure`
|
|
|
+ * script on supported platforms.
|
|
|
+ */
|
|
|
+#undef FT_CONFIG_OPTION_FORCE_INT64
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * If this macro is defined, do not try to use an assembler version of
|
|
|
+ * performance-critical functions (e.g., @FT_MulFix). You should only do
|
|
|
+ * that to verify that the assembler function works properly, or to execute
|
|
|
+ * benchmark tests of the various implementations.
|
|
|
+ */
|
|
|
+/* #define FT_CONFIG_OPTION_NO_ASSEMBLER */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * If this macro is defined, try to use an inlined assembler version of the
|
|
|
+ * @FT_MulFix function, which is a 'hotspot' when loading and hinting
|
|
|
+ * glyphs, and which should be executed as fast as possible.
|
|
|
+ *
|
|
|
+ * Note that if your compiler or CPU is not supported, this will default to
|
|
|
+ * the standard and portable implementation found in `ftcalc.c`.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_INLINE_MULFIX
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * LZW-compressed file support.
|
|
|
+ *
|
|
|
+ * FreeType now handles font files that have been compressed with the
|
|
|
+ * `compress` program. This is mostly used to parse many of the PCF
|
|
|
+ * files that come with various X11 distributions. The implementation
|
|
|
+ * uses NetBSD's `zopen` to partially uncompress the file on the fly (see
|
|
|
+ * `src/lzw/ftgzip.c`).
|
|
|
+ *
|
|
|
+ * Define this macro if you want to enable this 'feature'.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_USE_LZW
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Gzip-compressed file support.
|
|
|
+ *
|
|
|
+ * FreeType now handles font files that have been compressed with the
|
|
|
+ * `gzip` program. This is mostly used to parse many of the PCF files
|
|
|
+ * that come with XFree86. The implementation uses 'zlib' to partially
|
|
|
+ * uncompress the file on the fly (see `src/gzip/ftgzip.c`).
|
|
|
+ *
|
|
|
+ * Define this macro if you want to enable this 'feature'. See also the
|
|
|
+ * macro `FT_CONFIG_OPTION_SYSTEM_ZLIB` below.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_USE_ZLIB
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * ZLib library selection
|
|
|
+ *
|
|
|
+ * This macro is only used when `FT_CONFIG_OPTION_USE_ZLIB` is defined.
|
|
|
+ * It allows FreeType's 'ftgzip' component to link to the system's
|
|
|
+ * installation of the ZLib library. This is useful on systems like
|
|
|
+ * Unix or VMS where it generally is already available.
|
|
|
+ *
|
|
|
+ * If you let it undefined, the component will use its own copy of the
|
|
|
+ * zlib sources instead. These have been modified to be included
|
|
|
+ * directly within the component and **not** export external function
|
|
|
+ * names. This allows you to link any program with FreeType _and_ ZLib
|
|
|
+ * without linking conflicts.
|
|
|
+ *
|
|
|
+ * Do not `#undef` this macro here since the build system might define
|
|
|
+ * it for certain configurations only.
|
|
|
+ *
|
|
|
+ * If you use a build system like cmake or the `configure` script,
|
|
|
+ * options set by those programs have precedence, overwriting the value
|
|
|
+ * here with the configured one.
|
|
|
+ *
|
|
|
+ * If you use the GNU make build system directly (that is, without the
|
|
|
+ * `configure` script) and you define this macro, you also have to pass
|
|
|
+ * `SYSTEM_ZLIB=yes` as an argument to make.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_SYSTEM_ZLIB
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Bzip2-compressed file support.
|
|
|
+ *
|
|
|
+ * FreeType now handles font files that have been compressed with the
|
|
|
+ * `bzip2` program. This is mostly used to parse many of the PCF files
|
|
|
+ * that come with XFree86. The implementation uses `libbz2` to partially
|
|
|
+ * uncompress the file on the fly (see `src/bzip2/ftbzip2.c`). Contrary
|
|
|
+ * to gzip, bzip2 currently is not included and need to use the system
|
|
|
+ * available bzip2 implementation.
|
|
|
+ *
|
|
|
+ * Define this macro if you want to enable this 'feature'.
|
|
|
+ *
|
|
|
+ * If you use a build system like cmake or the `configure` script,
|
|
|
+ * options set by those programs have precedence, overwriting the value
|
|
|
+ * here with the configured one.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_USE_BZIP2
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define to disable the use of file stream functions and types, `FILE`,
|
|
|
+ * `fopen`, etc. Enables the use of smaller system libraries on embedded
|
|
|
+ * systems that have multiple system libraries, some with or without file
|
|
|
+ * stream support, in the cases where file stream support is not necessary
|
|
|
+ * such as memory loading of font files.
|
|
|
+ */
|
|
|
+/* #define FT_CONFIG_OPTION_DISABLE_STREAM_SUPPORT */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * PNG bitmap support.
|
|
|
+ *
|
|
|
+ * FreeType now handles loading color bitmap glyphs in the PNG format.
|
|
|
+ * This requires help from the external libpng library. Uncompressed
|
|
|
+ * color bitmaps do not need any external libraries and will be supported
|
|
|
+ * regardless of this configuration.
|
|
|
+ *
|
|
|
+ * Define this macro if you want to enable this 'feature'.
|
|
|
+ *
|
|
|
+ * If you use a build system like cmake or the `configure` script,
|
|
|
+ * options set by those programs have precedence, overwriting the value
|
|
|
+ * here with the configured one.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_USE_PNG
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * HarfBuzz support.
|
|
|
+ *
|
|
|
+ * FreeType uses the HarfBuzz library to improve auto-hinting of OpenType
|
|
|
+ * fonts. If available, many glyphs not directly addressable by a font's
|
|
|
+ * character map will be hinted also.
|
|
|
+ *
|
|
|
+ * Define this macro if you want to enable this 'feature'.
|
|
|
+ *
|
|
|
+ * If you use a build system like cmake or the `configure` script,
|
|
|
+ * options set by those programs have precedence, overwriting the value
|
|
|
+ * here with the configured one.
|
|
|
+ */
|
|
|
+/* #define FT_CONFIG_OPTION_USE_HARFBUZZ */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Brotli support.
|
|
|
+ *
|
|
|
+ * FreeType uses the Brotli library to provide support for decompressing
|
|
|
+ * WOFF2 streams.
|
|
|
+ *
|
|
|
+ * Define this macro if you want to enable this 'feature'.
|
|
|
+ *
|
|
|
+ * If you use a build system like cmake or the `configure` script,
|
|
|
+ * options set by those programs have precedence, overwriting the value
|
|
|
+ * here with the configured one.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_USE_BROTLI
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Glyph Postscript Names handling
|
|
|
+ *
|
|
|
+ * By default, FreeType 2 is compiled with the 'psnames' module. 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,
|
|
|
+ * but will not synthesize a missing Unicode charmap.
|
|
|
+ *
|
|
|
+ * - The Type~1 driver will not be able to synthesize 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
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Postscript Names to Unicode Values support
|
|
|
+ *
|
|
|
+ * By default, FreeType~2 is built with the 'psnames' module compiled in.
|
|
|
+ * Among other things, the module is used to convert a glyph name into a
|
|
|
+ * Unicode value. This is especially useful in order to synthesize on
|
|
|
+ * the fly a Unicode charmap from the CFF/Type~1 driver through a big
|
|
|
+ * table named the 'Adobe Glyph List' (AGL).
|
|
|
+ *
|
|
|
+ * Undefine this macro if you do not want the Adobe Glyph List compiled
|
|
|
+ * in your 'psnames' module. The Type~1 driver will not be able to
|
|
|
+ * synthesize a Unicode charmap out of the glyphs found in the fonts.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_ADOBE_GLYPH_LIST
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Support for Mac fonts
|
|
|
+ *
|
|
|
+ * Define this macro if you want support for outline fonts in Mac format
|
|
|
+ * (mac dfont, mac resource, macbinary containing a mac resource) on
|
|
|
+ * non-Mac platforms.
|
|
|
+ *
|
|
|
+ * Note that the 'FOND' resource isn't checked.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_MAC_FONTS
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Guessing methods to access embedded resource forks
|
|
|
+ *
|
|
|
+ * Enable extra Mac fonts support on non-Mac platforms (e.g., GNU/Linux).
|
|
|
+ *
|
|
|
+ * Resource forks which include fonts data are stored sometimes in
|
|
|
+ * locations which users or developers don't expected. In some cases,
|
|
|
+ * resource forks start with some offset from the head of a file. In
|
|
|
+ * other cases, the actual resource fork is stored in file different from
|
|
|
+ * what the user specifies. If this option is activated, FreeType tries
|
|
|
+ * to guess whether such offsets or different file names must be used.
|
|
|
+ *
|
|
|
+ * Note that normal, direct access of resource forks is controlled via
|
|
|
+ * the `FT_CONFIG_OPTION_MAC_FONTS` option.
|
|
|
+ */
|
|
|
+#ifdef FT_CONFIG_OPTION_MAC_FONTS
|
|
|
+#define FT_CONFIG_OPTION_GUESSING_EMBEDDED_RFORK
|
|
|
+#endif
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Allow the use of `FT_Incremental_Interface` to load typefaces that
|
|
|
+ * contain no glyph data, but supply it via a callback function. This is
|
|
|
+ * required by clients supporting document formats which supply font data
|
|
|
+ * incrementally as the document is parsed, such as the Ghostscript
|
|
|
+ * interpreter for the PostScript language.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_INCREMENTAL
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * The size in bytes of the render pool used by the scan-line converter to
|
|
|
+ * do all of its work.
|
|
|
+ */
|
|
|
+#define FT_RENDER_POOL_SIZE 16384L
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * FT_MAX_MODULES
|
|
|
+ *
|
|
|
+ * The maximum number of modules that can be registered in a single
|
|
|
+ * FreeType library object. 32~is the default.
|
|
|
+ */
|
|
|
+#define FT_MAX_MODULES 32
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Debug level
|
|
|
+ *
|
|
|
+ * FreeType can be compiled in debug or trace mode. In debug mode,
|
|
|
+ * errors are reported through the 'ftdebug' component. In trace mode,
|
|
|
+ * additional messages are sent to the standard output during execution.
|
|
|
+ *
|
|
|
+ * Define `FT_DEBUG_LEVEL_ERROR` to build the library in debug mode.
|
|
|
+ * Define `FT_DEBUG_LEVEL_TRACE` to build it in trace mode.
|
|
|
+ *
|
|
|
+ * Don't define any of these macros to compile in 'release' mode!
|
|
|
+ *
|
|
|
+ * Do not `#undef` these macros here since the build system might define
|
|
|
+ * them for certain configurations only.
|
|
|
+ */
|
|
|
+/* #define FT_DEBUG_LEVEL_ERROR */
|
|
|
+/* #define FT_DEBUG_LEVEL_TRACE */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Logging
|
|
|
+ *
|
|
|
+ * Compiling FreeType in debug or trace mode makes FreeType write error
|
|
|
+ * and trace log messages to `stderr`. Enabling this macro
|
|
|
+ * automatically forces the `FT_DEBUG_LEVEL_ERROR` and
|
|
|
+ * `FT_DEBUG_LEVEL_TRACE` macros and allows FreeType to write error and
|
|
|
+ * trace log messages to a file instead of `stderr`. For writing logs
|
|
|
+ * to a file, FreeType uses an the external `dlg` library (the source
|
|
|
+ * code is in `src/dlg`).
|
|
|
+ *
|
|
|
+ * This option needs a C99 compiler.
|
|
|
+ */
|
|
|
+/* #define FT_DEBUG_LOGGING */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Autofitter debugging
|
|
|
+ *
|
|
|
+ * If `FT_DEBUG_AUTOFIT` is defined, FreeType provides some means to
|
|
|
+ * control the autofitter behaviour for debugging purposes with global
|
|
|
+ * boolean variables (consequently, you should **never** enable this
|
|
|
+ * while compiling in 'release' mode):
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * af_debug_disable_horz_hints_
|
|
|
+ * af_debug_disable_vert_hints_
|
|
|
+ * af_debug_disable_blue_hints_
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ * Additionally, the following functions provide dumps of various
|
|
|
+ * internal autofit structures to stdout (using `printf`):
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * af_glyph_hints_dump_points
|
|
|
+ * af_glyph_hints_dump_segments
|
|
|
+ * af_glyph_hints_dump_edges
|
|
|
+ * af_glyph_hints_get_num_segments
|
|
|
+ * af_glyph_hints_get_segment_offset
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ * As an argument, they use another global variable:
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * af_debug_hints_
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ * Please have a look at the `ftgrid` demo program to see how those
|
|
|
+ * variables and macros should be used.
|
|
|
+ *
|
|
|
+ * Do not `#undef` these macros here since the build system might define
|
|
|
+ * them for certain configurations only.
|
|
|
+ */
|
|
|
+/* #define FT_DEBUG_AUTOFIT */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Memory Debugging
|
|
|
+ *
|
|
|
+ * FreeType now comes with an integrated memory debugger that is capable
|
|
|
+ * of detecting simple errors like memory leaks or double deletes. To
|
|
|
+ * compile it within your build of the library, you should define
|
|
|
+ * `FT_DEBUG_MEMORY` here.
|
|
|
+ *
|
|
|
+ * Note that the memory debugger is only activated at runtime when when
|
|
|
+ * the _environment_ variable `FT2_DEBUG_MEMORY` is defined also!
|
|
|
+ *
|
|
|
+ * Do not `#undef` this macro here since the build system might define it
|
|
|
+ * for certain configurations only.
|
|
|
+ */
|
|
|
+/* #define FT_DEBUG_MEMORY */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Module errors
|
|
|
+ *
|
|
|
+ * If this macro is set (which is _not_ the default), the higher byte of
|
|
|
+ * an error code gives the module in which the error has occurred, while
|
|
|
+ * the lower byte is the real error code.
|
|
|
+ *
|
|
|
+ * Setting this macro makes sense for debugging purposes only, since it
|
|
|
+ * would break source compatibility of certain programs that use
|
|
|
+ * FreeType~2.
|
|
|
+ *
|
|
|
+ * More details can be found in the files `ftmoderr.h` and `fterrors.h`.
|
|
|
+ */
|
|
|
+#undef FT_CONFIG_OPTION_USE_MODULE_ERRORS
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * OpenType SVG Glyph Support
|
|
|
+ *
|
|
|
+ * Setting this macro enables support for OpenType SVG glyphs. By
|
|
|
+ * default, FreeType can only fetch SVG documents. However, it can also
|
|
|
+ * render them if external rendering hook functions are plugged in at
|
|
|
+ * runtime.
|
|
|
+ *
|
|
|
+ * More details on the hooks can be found in file `otsvg.h`.
|
|
|
+ */
|
|
|
+#define FT_CONFIG_OPTION_SVG
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Error Strings
|
|
|
+ *
|
|
|
+ * If this macro is set, `FT_Error_String` will return meaningful
|
|
|
+ * descriptions. This is not enabled by default to reduce the overall
|
|
|
+ * size of FreeType.
|
|
|
+ *
|
|
|
+ * More details can be found in the file `fterrors.h`.
|
|
|
+ */
|
|
|
+/* #define FT_CONFIG_OPTION_ERROR_STRINGS */
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** S F N T D R I V E R C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_EMBEDDED_BITMAPS` if you want to support
|
|
|
+ * embedded bitmaps in all formats using the 'sfnt' module (namely
|
|
|
+ * TrueType~& OpenType).
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_EMBEDDED_BITMAPS
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_COLOR_LAYERS` if you want to support colored
|
|
|
+ * outlines (from the 'COLR'/'CPAL' tables) in all formats using the 'sfnt'
|
|
|
+ * module (namely TrueType~& OpenType).
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_COLOR_LAYERS
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_POSTSCRIPT_NAMES` if you want to be able to
|
|
|
+ * load and enumerate Postscript names of glyphs in a TrueType or OpenType
|
|
|
+ * file.
|
|
|
+ *
|
|
|
+ * Note that if you do not compile the 'psnames' module by undefining the
|
|
|
+ * above `FT_CONFIG_OPTION_POSTSCRIPT_NAMES` macro, the 'sfnt' module will
|
|
|
+ * contain additional code to read the PostScript name table from a font.
|
|
|
+ *
|
|
|
+ * (By default, the module uses 'psnames' to extract glyph names.)
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_POSTSCRIPT_NAMES
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_SFNT_NAMES` if your applications need to access
|
|
|
+ * the internal name table in a SFNT-based format like TrueType or
|
|
|
+ * OpenType. The name table contains various strings used to describe the
|
|
|
+ * font, like family name, copyright, version, etc. It does not contain
|
|
|
+ * any glyph name though.
|
|
|
+ *
|
|
|
+ * Accessing SFNT names is done through the functions declared in
|
|
|
+ * `ftsnames.h`.
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_SFNT_NAMES
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * TrueType CMap support
|
|
|
+ *
|
|
|
+ * Here you can fine-tune which TrueType CMap table format shall be
|
|
|
+ * supported.
|
|
|
+ */
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_0
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_2
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_4
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_6
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_8
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_10
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_12
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_13
|
|
|
+#define TT_CONFIG_CMAP_FORMAT_14
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** T R U E T Y P E D R I V E R C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_BYTECODE_INTERPRETER` if you want to compile a
|
|
|
+ * bytecode interpreter in the TrueType driver.
|
|
|
+ *
|
|
|
+ * By undefining this, you will only compile the code necessary to load
|
|
|
+ * TrueType glyphs without hinting.
|
|
|
+ *
|
|
|
+ * Do not `#undef` this macro here, since the build system might define it
|
|
|
+ * for certain configurations only.
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_SUBPIXEL_HINTING` if you want to compile
|
|
|
+ * subpixel hinting support into the TrueType driver. This modifies the
|
|
|
+ * TrueType hinting mechanism when anything but `FT_RENDER_MODE_MONO` is
|
|
|
+ * requested.
|
|
|
+ *
|
|
|
+ * In particular, it modifies the bytecode interpreter to interpret (or
|
|
|
+ * not) instructions in a certain way so that all TrueType fonts look like
|
|
|
+ * they do in a Windows ClearType (DirectWrite) environment. See [1] for a
|
|
|
+ * technical overview on what this means. See `ttinterp.h` for more
|
|
|
+ * details on this option.
|
|
|
+ *
|
|
|
+ * The new default mode focuses on applying a minimal set of rules to all
|
|
|
+ * fonts indiscriminately so that modern and web fonts render well while
|
|
|
+ * legacy fonts render okay. The corresponding interpreter version is v40.
|
|
|
+ * The so-called Infinality mode (v38) is no longer available in FreeType.
|
|
|
+ *
|
|
|
+ * By undefining these, you get rendering behavior like on Windows without
|
|
|
+ * ClearType, i.e., Windows XP without ClearType enabled and Win9x
|
|
|
+ * (interpreter version v35). Or not, depending on how much hinting blood
|
|
|
+ * and testing tears the font designer put into a given font. If you
|
|
|
+ * define one or both subpixel hinting options, you can switch between
|
|
|
+ * between v35 and the ones you define (using `FT_Property_Set`).
|
|
|
+ *
|
|
|
+ * This option requires `TT_CONFIG_OPTION_BYTECODE_INTERPRETER` to be
|
|
|
+ * defined.
|
|
|
+ *
|
|
|
+ * [1]
|
|
|
+ * https://www.microsoft.com/typography/cleartype/truetypecleartype.aspx
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_SUBPIXEL_HINTING
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED` to compile the
|
|
|
+ * TrueType glyph loader to use Apple's definition of how to handle
|
|
|
+ * component offsets in composite glyphs.
|
|
|
+ *
|
|
|
+ * Apple and MS disagree on the default behavior of component offsets in
|
|
|
+ * composites. Apple says that they should be scaled by the scaling
|
|
|
+ * factors in the transformation matrix (roughly, it's more complex) while
|
|
|
+ * MS says they should not. OpenType defines two bits in the composite
|
|
|
+ * flags array which can be used to disambiguate, but old fonts will not
|
|
|
+ * have them.
|
|
|
+ *
|
|
|
+ * https://www.microsoft.com/typography/otspec/glyf.htm
|
|
|
+ * https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6glyf.html
|
|
|
+ */
|
|
|
+#undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_GX_VAR_SUPPORT` if you want to include support
|
|
|
+ * for Apple's distortable font technology ('fvar', 'gvar', 'cvar', and
|
|
|
+ * 'avar' tables). Tagged 'Font Variations', this is now part of OpenType
|
|
|
+ * also. This has many similarities to Type~1 Multiple Masters support.
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_GX_VAR_SUPPORT
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_NO_BORING_EXPANSION` if you want to exclude
|
|
|
+ * support for 'boring' OpenType specification expansions.
|
|
|
+ *
|
|
|
+ * https://github.com/harfbuzz/boring-expansion-spec
|
|
|
+ *
|
|
|
+ * Right now, the following features are covered:
|
|
|
+ *
|
|
|
+ * - 'avar' version 2.0
|
|
|
+ *
|
|
|
+ * Most likely, this is a temporary configuration option to be removed in
|
|
|
+ * the near future, since it is assumed that eventually those features are
|
|
|
+ * added to the OpenType standard.
|
|
|
+ */
|
|
|
+/* #define TT_CONFIG_OPTION_NO_BORING_EXPANSION */
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define `TT_CONFIG_OPTION_BDF` if you want to include support for an
|
|
|
+ * embedded 'BDF~' table within SFNT-based bitmap formats.
|
|
|
+ */
|
|
|
+#define TT_CONFIG_OPTION_BDF
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Option `TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES` controls the maximum
|
|
|
+ * number of bytecode instructions executed for a single run of the
|
|
|
+ * bytecode interpreter, needed to prevent infinite loops. You don't want
|
|
|
+ * to change this except for very special situations (e.g., making a
|
|
|
+ * library fuzzer spend less time to handle broken fonts).
|
|
|
+ *
|
|
|
+ * It is not expected that this value is ever modified by a configuring
|
|
|
+ * script; instead, it gets surrounded with `#ifndef ... #endif` so that
|
|
|
+ * the value can be set as a preprocessor option on the compiler's command
|
|
|
+ * line.
|
|
|
+ */
|
|
|
+#ifndef TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES
|
|
|
+#define TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES 1000000L
|
|
|
+#endif
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** T Y P E 1 D R I V E R C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * `T1_MAX_DICT_DEPTH` is the maximum depth of nest dictionaries and arrays
|
|
|
+ * in the Type~1 stream (see `t1load.c`). A minimum of~4 is required.
|
|
|
+ */
|
|
|
+#define T1_MAX_DICT_DEPTH 5
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * `T1_MAX_SUBRS_CALLS` details the maximum number of nested sub-routine
|
|
|
+ * calls during glyph loading.
|
|
|
+ */
|
|
|
+#define T1_MAX_SUBRS_CALLS 16
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * `T1_MAX_CHARSTRING_OPERANDS` is the charstring stack's capacity. A
|
|
|
+ * minimum of~16 is required.
|
|
|
+ *
|
|
|
+ * The Chinese font 'MingTiEG-Medium' (covering the CNS 11643 character
|
|
|
+ * set) needs 256.
|
|
|
+ */
|
|
|
+#define T1_MAX_CHARSTRINGS_OPERANDS 256
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define this configuration macro if you want to prevent the compilation
|
|
|
+ * of the 't1afm' module, which is in charge of reading Type~1 AFM files
|
|
|
+ * into an existing face. Note that if set, the Type~1 driver will be
|
|
|
+ * unable to produce kerning distances.
|
|
|
+ */
|
|
|
+#undef T1_CONFIG_OPTION_NO_AFM
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Define this configuration macro if you want to prevent the compilation
|
|
|
+ * of the Multiple Masters font support in the Type~1 driver.
|
|
|
+ */
|
|
|
+#undef T1_CONFIG_OPTION_NO_MM_SUPPORT
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * `T1_CONFIG_OPTION_OLD_ENGINE` controls whether the pre-Adobe Type~1
|
|
|
+ * engine gets compiled into FreeType. If defined, it is possible to
|
|
|
+ * switch between the two engines using the `hinting-engine` property of
|
|
|
+ * the 'type1' driver module.
|
|
|
+ */
|
|
|
+/* #define T1_CONFIG_OPTION_OLD_ENGINE */
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** C F F D R I V E R C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Using `CFF_CONFIG_OPTION_DARKENING_PARAMETER_{X,Y}{1,2,3,4}` it is
|
|
|
+ * possible to set up the default values of the four control points that
|
|
|
+ * define the stem darkening behaviour of the (new) CFF engine. For more
|
|
|
+ * details please read the documentation of the `darkening-parameters`
|
|
|
+ * property (file `ftdriver.h`), which allows the control at run-time.
|
|
|
+ *
|
|
|
+ * Do **not** undefine these macros!
|
|
|
+ */
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 500
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 400
|
|
|
+
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 1000
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 275
|
|
|
+
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 1667
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 275
|
|
|
+
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 2333
|
|
|
+#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 0
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * `CFF_CONFIG_OPTION_OLD_ENGINE` controls whether the pre-Adobe CFF engine
|
|
|
+ * gets compiled into FreeType. If defined, it is possible to switch
|
|
|
+ * between the two engines using the `hinting-engine` property of the 'cff'
|
|
|
+ * driver module.
|
|
|
+ */
|
|
|
+/* #define CFF_CONFIG_OPTION_OLD_ENGINE */
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** P C F D R I V E R C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * There are many PCF fonts just called 'Fixed' which look completely
|
|
|
+ * different, and which have nothing to do with each other. When selecting
|
|
|
+ * 'Fixed' in KDE or Gnome one gets results that appear rather random, the
|
|
|
+ * style changes often if one changes the size and one cannot select some
|
|
|
+ * fonts at all. This option makes the 'pcf' module prepend the foundry
|
|
|
+ * name (plus a space) to the family name.
|
|
|
+ *
|
|
|
+ * We also check whether we have 'wide' characters; all put together, we
|
|
|
+ * get family names like 'Sony Fixed' or 'Misc Fixed Wide'.
|
|
|
+ *
|
|
|
+ * If this option is activated, it can be controlled with the
|
|
|
+ * `no-long-family-names` property of the 'pcf' driver module.
|
|
|
+ */
|
|
|
+/* #define PCF_CONFIG_OPTION_LONG_FAMILY_NAMES */
|
|
|
+
|
|
|
+
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+ /**** ****/
|
|
|
+ /**** A U T O F I T M O D U L E C O N F I G U R A T I O N ****/
|
|
|
+ /**** ****/
|
|
|
+ /*************************************************************************/
|
|
|
+ /*************************************************************************/
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Compile 'autofit' module with CJK (Chinese, Japanese, Korean) script
|
|
|
+ * support.
|
|
|
+ */
|
|
|
+#define AF_CONFIG_OPTION_CJK
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Compile 'autofit' module with fallback Indic script support, covering
|
|
|
+ * some scripts that the 'latin' submodule of the 'autofit' module doesn't
|
|
|
+ * (yet) handle. Currently, this needs option `AF_CONFIG_OPTION_CJK`.
|
|
|
+ */
|
|
|
+#ifdef AF_CONFIG_OPTION_CJK
|
|
|
+#define AF_CONFIG_OPTION_INDIC
|
|
|
+#endif
|
|
|
+
|
|
|
+
|
|
|
+ /**************************************************************************
|
|
|
+ *
|
|
|
+ * Use TrueType-like size metrics for 'light' auto-hinting.
|
|
|
+ *
|
|
|
+ * It is strongly recommended to avoid this option, which exists only to
|
|
|
+ * help some legacy applications retain its appearance and behaviour with
|
|
|
+ * respect to auto-hinted TrueType fonts.
|
|
|
+ *
|
|
|
+ * The very reason this option exists at all are GNU/Linux distributions
|
|
|
+ * like Fedora that did not un-patch the following change (which was
|
|
|
+ * present in FreeType between versions 2.4.6 and 2.7.1, inclusive).
|
|
|
+ *
|
|
|
+ * ```
|
|
|
+ * 2011-07-16 Steven Chu <[email protected]>
|
|
|
+ *
|
|
|
+ * [truetype] Fix metrics on size request for scalable fonts.
|
|
|
+ * ```
|
|
|
+ *
|
|
|
+ * This problematic commit is now reverted (more or less).
|
|
|
+ */
|
|
|
+/* #define AF_CONFIG_OPTION_TT_SIZE_METRICS */
|
|
|
+
|
|
|
+ /* */
|
|
|
+
|
|
|
+
|
|
|
+ /*
|
|
|
+ * This macro is obsolete. Support has been removed in FreeType version
|
|
|
+ * 2.5.
|
|
|
+ */
|
|
|
+/* #define FT_CONFIG_OPTION_OLD_INTERNALS */
|
|
|
+
|
|
|
+
|
|
|
+ /*
|
|
|
+ * The next two macros are defined if native TrueType hinting is
|
|
|
+ * requested by the definitions above. Don't change this.
|
|
|
+ */
|
|
|
+#ifdef TT_CONFIG_OPTION_BYTECODE_INTERPRETER
|
|
|
+#define TT_USE_BYTECODE_INTERPRETER
|
|
|
+#ifdef TT_CONFIG_OPTION_SUBPIXEL_HINTING
|
|
|
+#define TT_SUPPORT_SUBPIXEL_HINTING_MINIMAL
|
|
|
+#endif
|
|
|
+#endif
|
|
|
+
|
|
|
+
|
|
|
+ /*
|
|
|
+ * The TT_SUPPORT_COLRV1 macro is defined to indicate to clients that this
|
|
|
+ * version of FreeType has support for 'COLR' v1 API. This definition is
|
|
|
+ * useful to FreeType clients that want to build in support for 'COLR' v1
|
|
|
+ * depending on a tip-of-tree checkout before it is officially released in
|
|
|
+ * FreeType, and while the feature cannot yet be tested against using
|
|
|
+ * version macros. Don't change this macro. This may be removed once the
|
|
|
+ * feature is in a FreeType release version and version macros can be used
|
|
|
+ * to test for availability.
|
|
|
+ */
|
|
|
+#ifdef TT_CONFIG_OPTION_COLOR_LAYERS
|
|
|
+#define TT_SUPPORT_COLRV1
|
|
|
+#endif
|
|
|
+
|
|
|
+
|
|
|
+ /*
|
|
|
+ * Check CFF darkening parameters. The checks are the same as in function
|
|
|
+ * `cff_property_set` in file `cffdrivr.c`.
|
|
|
+ */
|
|
|
+#if CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 < 0 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 < 0 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 < 0 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 < 0 || \
|
|
|
+ \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 < 0 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 < 0 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 < 0 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 < 0 || \
|
|
|
+ \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 > \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 > \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 > \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 || \
|
|
|
+ \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 > 500 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 > 500 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 > 500 || \
|
|
|
+ CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 > 500
|
|
|
+#error "Invalid CFF darkening parameters!"
|
|
|
+#endif
|
|
|
+
|
|
|
+
|
|
|
+FT_END_HEADER
|
|
|
+
|
|
|
+#endif /* FTOPTION_H_ */
|
|
|
+
|
|
|
+
|
|
|
+/* END */
|