1 /**************************************************************************** 2 * 3 * ftoption.h 4 * 5 * User-selectable configuration macros (specification only). 6 * 7 * Copyright 1996-2018 by 8 * David Turner, Robert Wilhelm, and Werner Lemberg. 9 * 10 * This file is part of the FreeType project, and may only be used, 11 * modified, and distributed under the terms of the FreeType project 12 * license, LICENSE.TXT. By continuing to use, modify, or distribute 13 * this file you indicate that you have read the license and 14 * understand and accept it fully. 15 * 16 */ 17 18 19 #ifndef FTOPTION_H_ 20 #define FTOPTION_H_ 21 22 23 #include <ft2build.h> 24 25 26 FT_BEGIN_HEADER 27 28 /************************************************************************** 29 * 30 * USER-SELECTABLE CONFIGURATION MACROS 31 * 32 * This file contains the default configuration macro definitions for 33 * a standard build of the FreeType library. There are three ways to 34 * use this file to build project-specific versions of the library: 35 * 36 * - You can modify this file by hand, but this is not recommended in 37 * cases where you would like to build several versions of the 38 * library from a single source directory. 39 * 40 * - You can put a copy of this file in your build directory, more 41 * precisely in `$BUILD/freetype/config/ftoption.h', where `$BUILD' 42 * is the name of a directory that is included _before_ the FreeType 43 * include path during compilation. 44 * 45 * The default FreeType Makefiles and Jamfiles use the build 46 * directory `builds/<system>' by default, but you can easily change 47 * that for your own projects. 48 * 49 * - Copy the file <ft2build.h> to `$BUILD/ft2build.h' and modify it 50 * slightly to pre-define the macro FT_CONFIG_OPTIONS_H used to 51 * locate this file during the build. For example, 52 * 53 * { 54 * #define FT_CONFIG_OPTIONS_H <myftoptions.h> 55 * #include <freetype/config/ftheader.h> 56 * } 57 * 58 * will use `$BUILD/myftoptions.h' instead of this file for macro 59 * definitions. 60 * 61 * Note also that you can similarly pre-define the macro 62 * FT_CONFIG_MODULES_H used to locate the file listing of the modules 63 * that are statically linked to the library at compile time. By 64 * default, this file is <freetype/config/ftmodule.h>. 65 * 66 * We highly recommend using the third method whenever possible. 67 * 68 */ 69 70 71 /*************************************************************************/ 72 /*************************************************************************/ 73 /**** ****/ 74 /**** 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 ****/ 75 /**** ****/ 76 /*************************************************************************/ 77 /*************************************************************************/ 78 79 80 /*#************************************************************************ 81 * 82 * If you enable this configuration option, FreeType recognizes an 83 * environment variable called `FREETYPE_PROPERTIES', which can be used to 84 * control the various font drivers and modules. The controllable 85 * properties are listed in the section @properties. 86 * 87 * You have to undefine this configuration option on platforms that lack 88 * the concept of environment variables (and thus don't have the `getenv' 89 * function), for example Windows CE. 90 * 91 * `FREETYPE_PROPERTIES' has the following syntax form (broken here into 92 * multiple lines for better readability). 93 * 94 * { 95 * <optional whitespace> 96 * <module-name1> ':' 97 * <property-name1> '=' <property-value1> 98 * <whitespace> 99 * <module-name2> ':' 100 * <property-name2> '=' <property-value2> 101 * ... 102 * } 103 * 104 * Example: 105 * 106 * { 107 * FREETYPE_PROPERTIES=truetype:interpreter-version=35 \ 108 * cff:no-stem-darkening=1 \ 109 * autofitter:warping=1 110 * } 111 * 112 */ 113 /* ANDROID: disabled */ 114 /* #define FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES */ 115 116 117 /************************************************************************** 118 * 119 * Uncomment the line below if you want to activate LCD rendering 120 * technology similar to ClearType in this build of the library. This 121 * technology triples the resolution in the direction color subpixels. 122 * To mitigate color fringes inherent to this technology, you also need 123 * to explicitly set up LCD filtering. 124 * 125 * Note that this feature is covered by several Microsoft patents 126 * and should not be activated in any default build of the library. 127 * When this macro is not defined, FreeType offers alternative LCD 128 * rendering technology that produces excellent output without LCD 129 * filtering. 130 */ 131 /* #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING */ 132 133 134 /************************************************************************** 135 * 136 * Many compilers provide a non-ANSI 64-bit data type that can be used 137 * by FreeType to speed up some computations. However, this will create 138 * some problems when compiling the library in strict ANSI mode. 139 * 140 * For this reason, the use of 64-bit integers is normally disabled when 141 * the __STDC__ macro is defined. You can however disable this by 142 * defining the macro FT_CONFIG_OPTION_FORCE_INT64 here. 143 * 144 * For most compilers, this will only create compilation warnings when 145 * building the library. 146 * 147 * ObNote: The compiler-specific 64-bit integers are detected in the 148 * file `ftconfig.h' either statically or through the 149 * `configure' script on supported platforms. 150 */ 151 #undef FT_CONFIG_OPTION_FORCE_INT64 152 153 154 /************************************************************************** 155 * 156 * If this macro is defined, do not try to use an assembler version of 157 * performance-critical functions (e.g. FT_MulFix). You should only do 158 * that to verify that the assembler function works properly, or to 159 * execute benchmark tests of the various implementations. 160 */ 161 /* #define FT_CONFIG_OPTION_NO_ASSEMBLER */ 162 163 164 /************************************************************************** 165 * 166 * If this macro is defined, try to use an inlined assembler version of 167 * the `FT_MulFix' function, which is a `hotspot' when loading and 168 * hinting glyphs, and which should be executed as fast as possible. 169 * 170 * Note that if your compiler or CPU is not supported, this will default 171 * to the standard and portable implementation found in `ftcalc.c'. 172 */ 173 #define FT_CONFIG_OPTION_INLINE_MULFIX 174 175 176 /************************************************************************** 177 * 178 * LZW-compressed file support. 179 * 180 * FreeType now handles font files that have been compressed with the 181 * `compress' program. This is mostly used to parse many of the PCF 182 * files that come with various X11 distributions. The implementation 183 * uses NetBSD's `zopen' to partially uncompress the file on the fly 184 * (see src/lzw/ftgzip.c). 185 * 186 * Define this macro if you want to enable this `feature'. 187 */ 188 #define FT_CONFIG_OPTION_USE_LZW 189 190 191 /************************************************************************** 192 * 193 * Gzip-compressed file support. 194 * 195 * FreeType now handles font files that have been compressed with the 196 * `gzip' program. This is mostly used to parse many of the PCF files 197 * that come with XFree86. The implementation uses `zlib' to 198 * partially uncompress the file on the fly (see src/gzip/ftgzip.c). 199 * 200 * Define this macro if you want to enable this `feature'. See also 201 * the macro FT_CONFIG_OPTION_SYSTEM_ZLIB below. 202 */ 203 #define FT_CONFIG_OPTION_USE_ZLIB 204 205 206 /************************************************************************** 207 * 208 * ZLib library selection 209 * 210 * This macro is only used when FT_CONFIG_OPTION_USE_ZLIB is defined. 211 * It allows FreeType's `ftgzip' component to link to the system's 212 * installation of the ZLib library. This is useful on systems like 213 * Unix or VMS where it generally is already available. 214 * 215 * If you let it undefined, the component will use its own copy 216 * of the zlib sources instead. These have been modified to be 217 * included directly within the component and *not* export external 218 * function names. This allows you to link any program with FreeType 219 * _and_ ZLib without linking conflicts. 220 * 221 * Do not #undef this macro here since the build system might define 222 * it for certain configurations only. 223 * 224 * If you use a build system like cmake or the `configure' script, 225 * options set by those programs have precendence, overwriting the 226 * value here with the configured one. 227 */ 228 /* #define FT_CONFIG_OPTION_SYSTEM_ZLIB */ 229 230 231 /************************************************************************** 232 * 233 * Bzip2-compressed file support. 234 * 235 * FreeType now handles font files that have been compressed with the 236 * `bzip2' program. This is mostly used to parse many of the PCF 237 * files that come with XFree86. The implementation uses `libbz2' to 238 * partially uncompress the file on the fly (see src/bzip2/ftbzip2.c). 239 * Contrary to gzip, bzip2 currently is not included and need to use 240 * the system available bzip2 implementation. 241 * 242 * Define this macro if you want to enable this `feature'. 243 * 244 * If you use a build system like cmake or the `configure' script, 245 * options set by those programs have precendence, overwriting the 246 * value here with the configured one. 247 */ 248 /* #define FT_CONFIG_OPTION_USE_BZIP2 */ 249 250 251 /************************************************************************** 252 * 253 * Define to disable the use of file stream functions and types, FILE, 254 * fopen() etc. Enables the use of smaller system libraries on embedded 255 * systems that have multiple system libraries, some with or without 256 * file stream support, in the cases where file stream support is not 257 * necessary such as memory loading of font files. 258 */ 259 /* #define FT_CONFIG_OPTION_DISABLE_STREAM_SUPPORT */ 260 261 262 /************************************************************************** 263 * 264 * PNG bitmap support. 265 * 266 * FreeType now handles loading color bitmap glyphs in the PNG format. 267 * This requires help from the external libpng library. Uncompressed 268 * color bitmaps do not need any external libraries and will be 269 * supported regardless of this configuration. 270 * 271 * Define this macro if you want to enable this `feature'. 272 * 273 * If you use a build system like cmake or the `configure' script, 274 * options set by those programs have precendence, overwriting the 275 * value here with the configured one. 276 */ 277 /* ANDROID: enabled */ 278 #define FT_CONFIG_OPTION_USE_PNG 279 280 281 /************************************************************************** 282 * 283 * HarfBuzz support. 284 * 285 * FreeType uses the HarfBuzz library to improve auto-hinting of 286 * OpenType fonts. If available, many glyphs not directly addressable 287 * by a font's character map will be hinted also. 288 * 289 * Define this macro if you want to enable this `feature'. 290 * 291 * If you use a build system like cmake or the `configure' script, 292 * options set by those programs have precendence, overwriting the 293 * value here with the configured one. 294 */ 295 /* #define FT_CONFIG_OPTION_USE_HARFBUZZ */ 296 297 298 /************************************************************************** 299 * 300 * Glyph Postscript Names handling 301 * 302 * By default, FreeType 2 is compiled with the `psnames' module. This 303 * module is in charge of converting a glyph name string into a 304 * Unicode value, or return a Macintosh standard glyph name for the 305 * use with the TrueType `post' table. 306 * 307 * Undefine this macro if you do not want `psnames' compiled in your 308 * build of FreeType. This has the following effects: 309 * 310 * - The TrueType driver will provide its own set of glyph names, 311 * if you build it to support postscript names in the TrueType 312 * `post' table, but will not synthesize a missing Unicode charmap. 313 * 314 * - The Type 1 driver will not be able to synthesize a Unicode 315 * charmap out of the glyphs found in the fonts. 316 * 317 * You would normally undefine this configuration macro when building 318 * a version of FreeType that doesn't contain a Type 1 or CFF driver. 319 */ 320 #define FT_CONFIG_OPTION_POSTSCRIPT_NAMES 321 322 323 /************************************************************************** 324 * 325 * Postscript Names to Unicode Values support 326 * 327 * By default, FreeType 2 is built with the `PSNames' module compiled 328 * in. Among other things, the module is used to convert a glyph name 329 * into a Unicode value. This is especially useful in order to 330 * synthesize on the fly a Unicode charmap from the CFF/Type 1 driver 331 * through a big table named the `Adobe Glyph List' (AGL). 332 * 333 * Undefine this macro if you do not want the Adobe Glyph List 334 * compiled in your `PSNames' module. The Type 1 driver will not be 335 * able to synthesize a Unicode charmap out of the glyphs found in the 336 * fonts. 337 */ 338 #define FT_CONFIG_OPTION_ADOBE_GLYPH_LIST 339 340 341 /************************************************************************** 342 * 343 * Support for Mac fonts 344 * 345 * Define this macro if you want support for outline fonts in Mac 346 * format (mac dfont, mac resource, macbinary containing a mac 347 * resource) on non-Mac platforms. 348 * 349 * Note that the `FOND' resource isn't checked. 350 */ 351 #define FT_CONFIG_OPTION_MAC_FONTS 352 353 354 /************************************************************************** 355 * 356 * Guessing methods to access embedded resource forks 357 * 358 * Enable extra Mac fonts support on non-Mac platforms (e.g., GNU/Linux). 359 * 360 * Resource forks which include fonts data are stored sometimes in 361 * locations which users or developers don't expected. In some cases, 362 * resource forks start with some offset from the head of a file. In 363 * other cases, the actual resource fork is stored in file different 364 * from what the user specifies. If this option is activated, 365 * FreeType tries to guess whether such offsets or different file 366 * names must be used. 367 * 368 * Note that normal, direct access of resource forks is controlled via 369 * the FT_CONFIG_OPTION_MAC_FONTS option. 370 */ 371 #ifdef FT_CONFIG_OPTION_MAC_FONTS 372 #define FT_CONFIG_OPTION_GUESSING_EMBEDDED_RFORK 373 #endif 374 375 376 /************************************************************************** 377 * 378 * Allow the use of FT_Incremental_Interface to load typefaces that 379 * contain no glyph data, but supply it via a callback function. 380 * This is required by clients supporting document formats which 381 * supply font data incrementally as the document is parsed, such 382 * as the Ghostscript interpreter for the PostScript language. 383 */ 384 /* ANDROID: disabled */ 385 /* #define FT_CONFIG_OPTION_INCREMENTAL */ 386 387 388 /************************************************************************** 389 * 390 * The size in bytes of the render pool used by the scan-line converter 391 * to do all of its work. 392 */ 393 #define FT_RENDER_POOL_SIZE 16384L 394 395 396 /************************************************************************** 397 * 398 * FT_MAX_MODULES 399 * 400 * The maximum number of modules that can be registered in a single 401 * FreeType library object. 32 is the default. 402 */ 403 #define FT_MAX_MODULES 32 404 405 406 /************************************************************************** 407 * 408 * Debug level 409 * 410 * FreeType can be compiled in debug or trace mode. In debug mode, 411 * errors are reported through the `ftdebug' component. In trace 412 * mode, additional messages are sent to the standard output during 413 * execution. 414 * 415 * Define FT_DEBUG_LEVEL_ERROR to build the library in debug mode. 416 * Define FT_DEBUG_LEVEL_TRACE to build it in trace mode. 417 * 418 * Don't define any of these macros to compile in `release' mode! 419 * 420 * Do not #undef these macros here since the build system might define 421 * them for certain configurations only. 422 */ 423 /* #define FT_DEBUG_LEVEL_ERROR */ 424 /* #define FT_DEBUG_LEVEL_TRACE */ 425 426 427 /************************************************************************** 428 * 429 * Autofitter debugging 430 * 431 * If FT_DEBUG_AUTOFIT is defined, FreeType provides some means to 432 * control the autofitter behaviour for debugging purposes with global 433 * boolean variables (consequently, you should *never* enable this 434 * while compiling in `release' mode): 435 * 436 * { 437 * _af_debug_disable_horz_hints 438 * _af_debug_disable_vert_hints 439 * _af_debug_disable_blue_hints 440 * } 441 * 442 * Additionally, the following functions provide dumps of various 443 * internal autofit structures to stdout (using `printf'): 444 * 445 * { 446 * af_glyph_hints_dump_points 447 * af_glyph_hints_dump_segments 448 * af_glyph_hints_dump_edges 449 * af_glyph_hints_get_num_segments 450 * af_glyph_hints_get_segment_offset 451 * } 452 * 453 * As an argument, they use another global variable: 454 * 455 * { 456 * _af_debug_hints 457 * } 458 * 459 * Please have a look at the `ftgrid' demo program to see how those 460 * variables and macros should be used. 461 * 462 * Do not #undef these macros here since the build system might define 463 * them for certain configurations only. 464 */ 465 /* #define FT_DEBUG_AUTOFIT */ 466 467 468 /************************************************************************** 469 * 470 * Memory Debugging 471 * 472 * FreeType now comes with an integrated memory debugger that is 473 * capable of detecting simple errors like memory leaks or double 474 * deletes. To compile it within your build of the library, you 475 * should define FT_DEBUG_MEMORY here. 476 * 477 * Note that the memory debugger is only activated at runtime when 478 * when the _environment_ variable `FT2_DEBUG_MEMORY' is defined also! 479 * 480 * Do not #undef this macro here since the build system might define 481 * it for certain configurations only. 482 */ 483 /* #define FT_DEBUG_MEMORY */ 484 485 486 /************************************************************************** 487 * 488 * Module errors 489 * 490 * If this macro is set (which is _not_ the default), the higher byte 491 * of an error code gives the module in which the error has occurred, 492 * while the lower byte is the real error code. 493 * 494 * Setting this macro makes sense for debugging purposes only, since 495 * it would break source compatibility of certain programs that use 496 * FreeType 2. 497 * 498 * More details can be found in the files ftmoderr.h and fterrors.h. 499 */ 500 #undef FT_CONFIG_OPTION_USE_MODULE_ERRORS 501 502 503 /*************************************************************************/ 504 /*************************************************************************/ 505 /**** ****/ 506 /**** S F N T D R I V E R C O N F I G U R A T I O N ****/ 507 /**** ****/ 508 /*************************************************************************/ 509 /*************************************************************************/ 510 511 512 /************************************************************************** 513 * 514 * Define TT_CONFIG_OPTION_EMBEDDED_BITMAPS if you want to support 515 * embedded bitmaps in all formats using the SFNT module (namely 516 * TrueType & OpenType). 517 */ 518 #define TT_CONFIG_OPTION_EMBEDDED_BITMAPS 519 520 521 /************************************************************************** 522 * 523 * Define TT_CONFIG_OPTION_COLOR_LAYERS if you want to support coloured 524 * outlines (from the COLR/CPAL tables) in all formats using the SFNT 525 * module (namely TrueType & OpenType). 526 */ 527 #define TT_CONFIG_OPTION_COLOR_LAYERS 528 529 530 /************************************************************************** 531 * 532 * Define TT_CONFIG_OPTION_POSTSCRIPT_NAMES if you want to be able to 533 * load and enumerate the glyph Postscript names in a TrueType or 534 * OpenType file. 535 * 536 * Note that when you do not compile the `PSNames' module by undefining 537 * the above FT_CONFIG_OPTION_POSTSCRIPT_NAMES, the `sfnt' module will 538 * contain additional code used to read the PS Names table from a font. 539 * 540 * (By default, the module uses `PSNames' to extract glyph names.) 541 */ 542 #define TT_CONFIG_OPTION_POSTSCRIPT_NAMES 543 544 545 /************************************************************************** 546 * 547 * Define TT_CONFIG_OPTION_SFNT_NAMES if your applications need to 548 * access the internal name table in a SFNT-based format like TrueType 549 * or OpenType. The name table contains various strings used to 550 * describe the font, like family name, copyright, version, etc. It 551 * does not contain any glyph name though. 552 * 553 * Accessing SFNT names is done through the functions declared in 554 * `ftsnames.h'. 555 */ 556 #define TT_CONFIG_OPTION_SFNT_NAMES 557 558 559 /************************************************************************** 560 * 561 * TrueType CMap support 562 * 563 * Here you can fine-tune which TrueType CMap table format shall be 564 * supported. 565 */ 566 #define TT_CONFIG_CMAP_FORMAT_0 567 #define TT_CONFIG_CMAP_FORMAT_2 568 #define TT_CONFIG_CMAP_FORMAT_4 569 #define TT_CONFIG_CMAP_FORMAT_6 570 #define TT_CONFIG_CMAP_FORMAT_8 571 #define TT_CONFIG_CMAP_FORMAT_10 572 #define TT_CONFIG_CMAP_FORMAT_12 573 #define TT_CONFIG_CMAP_FORMAT_13 574 #define TT_CONFIG_CMAP_FORMAT_14 575 576 577 /*************************************************************************/ 578 /*************************************************************************/ 579 /**** ****/ 580 /**** 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 ****/ 581 /**** ****/ 582 /*************************************************************************/ 583 /*************************************************************************/ 584 585 /************************************************************************** 586 * 587 * Define TT_CONFIG_OPTION_BYTECODE_INTERPRETER if you want to compile 588 * a bytecode interpreter in the TrueType driver. 589 * 590 * By undefining this, you will only compile the code necessary to load 591 * TrueType glyphs without hinting. 592 * 593 * Do not #undef this macro here, since the build system might 594 * define it for certain configurations only. 595 */ 596 #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER 597 598 599 /************************************************************************** 600 * 601 * Define TT_CONFIG_OPTION_SUBPIXEL_HINTING if you want to compile 602 * subpixel hinting support into the TrueType driver. This modifies the 603 * TrueType hinting mechanism when anything but FT_RENDER_MODE_MONO is 604 * requested. 605 * 606 * In particular, it modifies the bytecode interpreter to interpret (or 607 * not) instructions in a certain way so that all TrueType fonts look 608 * like they do in a Windows ClearType (DirectWrite) environment. See 609 * [1] for a technical overview on what this means. See `ttinterp.h' 610 * for more details on the LEAN option. 611 * 612 * There are three possible values. 613 * 614 * Value 1: 615 * This value is associated with the `Infinality' moniker, 616 * contributed by an individual nicknamed Infinality with the goal of 617 * making TrueType fonts render better than on Windows. A high 618 * amount of configurability and flexibility, down to rules for 619 * single glyphs in fonts, but also very slow. Its experimental and 620 * slow nature and the original developer losing interest meant that 621 * this option was never enabled in default builds. 622 * 623 * The corresponding interpreter version is v38. 624 * 625 * Value 2: 626 * The new default mode for the TrueType driver. The Infinality code 627 * base was stripped to the bare minimum and all configurability 628 * removed in the name of speed and simplicity. The configurability 629 * was mainly aimed at legacy fonts like Arial, Times New Roman, or 630 * Courier. Legacy fonts are fonts that modify vertical stems to 631 * achieve clean black-and-white bitmaps. The new mode focuses on 632 * applying a minimal set of rules to all fonts indiscriminately so 633 * that modern and web fonts render well while legacy fonts render 634 * okay. 635 * 636 * The corresponding interpreter version is v40. 637 * 638 * Value 3: 639 * Compile both, making both v38 and v40 available (the latter is the 640 * default). 641 * 642 * By undefining these, you get rendering behavior like on Windows 643 * without ClearType, i.e., Windows XP without ClearType enabled and 644 * Win9x (interpreter version v35). Or not, depending on how much 645 * hinting blood and testing tears the font designer put into a given 646 * font. If you define one or both subpixel hinting options, you can 647 * switch between between v35 and the ones you define (using 648 * `FT_Property_Set'). 649 * 650 * This option requires TT_CONFIG_OPTION_BYTECODE_INTERPRETER to be 651 * defined. 652 * 653 * [1] https://www.microsoft.com/typography/cleartype/truetypecleartype.aspx 654 */ 655 /* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING 1 */ 656 657 /* ANDROID: disabled */ 658 /* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING 2 */ 659 660 /* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING ( 1 | 2 ) */ 661 662 663 /************************************************************************** 664 * 665 * Define TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED to compile the 666 * TrueType glyph loader to use Apple's definition of how to handle 667 * component offsets in composite glyphs. 668 * 669 * Apple and MS disagree on the default behavior of component offsets 670 * in composites. Apple says that they should be scaled by the scaling 671 * factors in the transformation matrix (roughly, it's more complex) 672 * while MS says they should not. OpenType defines two bits in the 673 * composite flags array which can be used to disambiguate, but old 674 * fonts will not have them. 675 * 676 * https://www.microsoft.com/typography/otspec/glyf.htm 677 * https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6glyf.html 678 */ 679 #undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED 680 681 682 /************************************************************************** 683 * 684 * Define TT_CONFIG_OPTION_GX_VAR_SUPPORT if you want to include 685 * support for Apple's distortable font technology (fvar, gvar, cvar, 686 * and avar tables). This has many similarities to Type 1 Multiple 687 * Masters support. 688 */ 689 #define TT_CONFIG_OPTION_GX_VAR_SUPPORT 690 691 692 /************************************************************************** 693 * 694 * Define TT_CONFIG_OPTION_BDF if you want to include support for 695 * an embedded `BDF ' table within SFNT-based bitmap formats. 696 */ 697 #define TT_CONFIG_OPTION_BDF 698 699 700 /************************************************************************** 701 * 702 * Option TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES controls the maximum 703 * number of bytecode instructions executed for a single run of the 704 * bytecode interpreter, needed to prevent infinite loops. You don't 705 * want to change this except for very special situations (e.g., making 706 * a library fuzzer spend less time to handle broken fonts). 707 * 708 * It is not expected that this value is ever modified by a configuring 709 * script; instead, it gets surrounded with #ifndef ... #endif so that 710 * the value can be set as a preprocessor option on the compiler's 711 * command line. 712 */ 713 #ifndef TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES 714 #define TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES 1000000L 715 #endif 716 717 718 /*************************************************************************/ 719 /*************************************************************************/ 720 /**** ****/ 721 /**** T Y P E 1 D R I V E R C O N F I G U R A T I O N ****/ 722 /**** ****/ 723 /*************************************************************************/ 724 /*************************************************************************/ 725 726 727 /************************************************************************** 728 * 729 * T1_MAX_DICT_DEPTH is the maximum depth of nest dictionaries and 730 * arrays in the Type 1 stream (see t1load.c). A minimum of 4 is 731 * required. 732 */ 733 #define T1_MAX_DICT_DEPTH 5 734 735 736 /************************************************************************** 737 * 738 * T1_MAX_SUBRS_CALLS details the maximum number of nested sub-routine 739 * calls during glyph loading. 740 */ 741 #define T1_MAX_SUBRS_CALLS 16 742 743 744 /************************************************************************** 745 * 746 * T1_MAX_CHARSTRING_OPERANDS is the charstring stack's capacity. A 747 * minimum of 16 is required. 748 * 749 * The Chinese font MingTiEG-Medium (CNS 11643 character set) needs 256. 750 */ 751 #define T1_MAX_CHARSTRINGS_OPERANDS 256 752 753 754 /************************************************************************** 755 * 756 * Define this configuration macro if you want to prevent the 757 * compilation of `t1afm', which is in charge of reading Type 1 AFM 758 * files into an existing face. Note that if set, the T1 driver will be 759 * unable to produce kerning distances. 760 */ 761 #undef T1_CONFIG_OPTION_NO_AFM 762 763 764 /************************************************************************** 765 * 766 * Define this configuration macro if you want to prevent the 767 * compilation of the Multiple Masters font support in the Type 1 768 * driver. 769 */ 770 #undef T1_CONFIG_OPTION_NO_MM_SUPPORT 771 772 773 /************************************************************************** 774 * 775 * T1_CONFIG_OPTION_OLD_ENGINE controls whether the pre-Adobe Type 1 776 * engine gets compiled into FreeType. If defined, it is possible to 777 * switch between the two engines using the `hinting-engine' property of 778 * the type1 driver module. 779 */ 780 /* #define T1_CONFIG_OPTION_OLD_ENGINE */ 781 782 783 /*************************************************************************/ 784 /*************************************************************************/ 785 /**** ****/ 786 /**** C F F D R I V E R C O N F I G U R A T I O N ****/ 787 /**** ****/ 788 /*************************************************************************/ 789 /*************************************************************************/ 790 791 792 /************************************************************************** 793 * 794 * Using CFF_CONFIG_OPTION_DARKENING_PARAMETER_{X,Y}{1,2,3,4} it is 795 * possible to set up the default values of the four control points that 796 * define the stem darkening behaviour of the (new) CFF engine. For 797 * more details please read the documentation of the 798 * `darkening-parameters' property (file `ftdriver.h'), which allows the 799 * control at run-time. 800 * 801 * Do *not* undefine these macros! 802 */ 803 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 500 804 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 400 805 806 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 1000 807 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 275 808 809 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 1667 810 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 275 811 812 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 2333 813 #define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 0 814 815 816 /************************************************************************** 817 * 818 * CFF_CONFIG_OPTION_OLD_ENGINE controls whether the pre-Adobe CFF 819 * engine gets compiled into FreeType. If defined, it is possible to 820 * switch between the two engines using the `hinting-engine' property of 821 * the cff driver module. 822 */ 823 /* #define CFF_CONFIG_OPTION_OLD_ENGINE */ 824 825 826 /*************************************************************************/ 827 /*************************************************************************/ 828 /**** ****/ 829 /**** P C F D R I V E R C O N F I G U R A T I O N ****/ 830 /**** ****/ 831 /*************************************************************************/ 832 /*************************************************************************/ 833 834 835 /************************************************************************** 836 * 837 * There are many PCF fonts just called `Fixed' which look completely 838 * different, and which have nothing to do with each other. When 839 * selecting `Fixed' in KDE or Gnome one gets results that appear rather 840 * random, the style changes often if one changes the size and one 841 * cannot select some fonts at all. This option makes the PCF module 842 * prepend the foundry name (plus a space) to the family name. 843 * 844 * We also check whether we have `wide' characters; all put together, we 845 * get family names like `Sony Fixed' or `Misc Fixed Wide'. 846 * 847 * If this option is activated, it can be controlled with the 848 * `no-long-family-names' property of the pcf driver module. 849 */ 850 /* #define PCF_CONFIG_OPTION_LONG_FAMILY_NAMES */ 851 852 853 /*************************************************************************/ 854 /*************************************************************************/ 855 /**** ****/ 856 /**** 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 ****/ 857 /**** ****/ 858 /*************************************************************************/ 859 /*************************************************************************/ 860 861 862 /************************************************************************** 863 * 864 * Compile autofit module with CJK (Chinese, Japanese, Korean) script 865 * support. 866 */ 867 #define AF_CONFIG_OPTION_CJK 868 869 /************************************************************************** 870 * 871 * Compile autofit module with fallback Indic script support, covering 872 * some scripts that the `latin' submodule of the autofit module doesn't 873 * (yet) handle. 874 */ 875 #define AF_CONFIG_OPTION_INDIC 876 877 /************************************************************************** 878 * 879 * Compile autofit module with warp hinting. The idea of the warping 880 * code is to slightly scale and shift a glyph within a single dimension 881 * so that as much of its segments are aligned (more or less) on the 882 * grid. To find out the optimal scaling and shifting value, various 883 * parameter combinations are tried and scored. 884 * 885 * This experimental option is active only if the rendering mode is 886 * FT_RENDER_MODE_LIGHT; you can switch warping on and off with the 887 * `warping' property of the auto-hinter (see file `ftdriver.h' for more 888 * information; by default it is switched off). 889 */ 890 #define AF_CONFIG_OPTION_USE_WARPER 891 892 /************************************************************************** 893 * 894 * Use TrueType-like size metrics for `light' auto-hinting. 895 * 896 * It is strongly recommended to avoid this option, which exists only to 897 * help some legacy applications retain its appearance and behaviour 898 * with respect to auto-hinted TrueType fonts. 899 * 900 * The very reason this option exists at all are GNU/Linux distributions 901 * like Fedora that did not un-patch the following change (which was 902 * present in FreeType between versions 2.4.6 and 2.7.1, inclusive). 903 * 904 * { 905 * 2011-07-16 Steven Chu <steven.f.chu@gmail.com> 906 * 907 * [truetype] Fix metrics on size request for scalable fonts. 908 * } 909 * 910 * This problematic commit is now reverted (more or less). 911 */ 912 /* #define AF_CONFIG_OPTION_TT_SIZE_METRICS */ 913 914 /* */ 915 916 917 /* 918 * This macro is obsolete. Support has been removed in FreeType 919 * version 2.5. 920 */ 921 /* #define FT_CONFIG_OPTION_OLD_INTERNALS */ 922 923 924 /* 925 * This macro is defined if native TrueType hinting is requested by the 926 * definitions above. 927 */ 928 #ifdef TT_CONFIG_OPTION_BYTECODE_INTERPRETER 929 #define TT_USE_BYTECODE_INTERPRETER 930 931 #ifdef TT_CONFIG_OPTION_SUBPIXEL_HINTING 932 #if TT_CONFIG_OPTION_SUBPIXEL_HINTING & 1 933 #define TT_SUPPORT_SUBPIXEL_HINTING_INFINALITY 934 #endif 935 936 #if TT_CONFIG_OPTION_SUBPIXEL_HINTING & 2 937 #define TT_SUPPORT_SUBPIXEL_HINTING_MINIMAL 938 #endif 939 #endif 940 #endif 941 942 943 /* 944 * Check CFF darkening parameters. The checks are the same as in function 945 * `cff_property_set' in file `cffdrivr.c'. 946 */ 947 #if CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 < 0 || \ 948 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 < 0 || \ 949 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 < 0 || \ 950 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 < 0 || \ 951 \ 952 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 < 0 || \ 953 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 < 0 || \ 954 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 < 0 || \ 955 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 < 0 || \ 956 \ 957 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 > \ 958 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 || \ 959 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 > \ 960 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 || \ 961 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 > \ 962 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 || \ 963 \ 964 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 > 500 || \ 965 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 > 500 || \ 966 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 > 500 || \ 967 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 > 500 968 #error "Invalid CFF darkening parameters!" 969 #endif 970 971 FT_END_HEADER 972 973 974 #endif /* FTOPTION_H_ */ 975 976 977 /* END */ 978